Protect4S - VM User Guide

Protect4S - VM User Guide
Introduction
Pre-conditions and installation
Protect4S VM Software Installation
- Add-On Installation, import support packages and upgrade
- Installation post-processing
Create Protect4S VM users and roles
Check and set Application settings
Protect4S VM Menu
Execute the Quick setup
- Company
- Systems
  Creating an ABAP system
  Creating a JAVA system
  Creating a BusinessObjects BI system
  Creating a HANA standalone system
  Creating a SAP Web Dispatcher system
  Creating a SAProuter system
  Creating a SAP Cloud Connector system
  SAPControl security settings
Create a project
- New project
- New Scan
Check Template
Contact persons and Scan subscription
- Contact persons
- Scan subscriptions
Reports
Mitigation of Vulnerabilities
- Mitigation menu
Check exemptions
SIEM Interface
Integration
- Incident Management
Information and support
Deinstallation
Appendix A: Troubleshooting Satellite System connection issues
Appendix B: Installation database libraries
Appendix C: satellite system Communication Ports
Appendix D: Protect4S VM SICF Services
Appendix E: using a server group
Appendix F System context
Appendix G DNS resolving
Appendix H Dump in Scan subsciptions
Appendix I HTTPURLLOC table
Appendix J - Risk Matrix
Appendix K - Short dump function module "PFL_GET_SINGLE_PARAMETER" not found
FAQs
Contact us

Powered by GitBook

On this page

Was this helpful?

Introduction

Protect4S VM place in SAP system landscape

PreviousSupport NextPre-conditions and installation

Last updated 1 year ago

Protect4S VM is delivered as a removable SAP Add-On. It is installed using the SAINT transaction in client 000.

The SAP system on which protect4S VM is installed is called: Protect4S system.
A SAP system that must be checked for vulnerabilities by Protect4S VM is called: satellite system.