Split (1)

train · 3.93k rows

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.

header stringlengths 12 160	content stringlengths 15 265k
## 6 Network and Communication Security	## 6 Network and Communication Security Your network infrastructure is extremely important in protecting your system. Your network needs to support the communication necessary for your business needs without allowing unauthorized access. A well-defined network topology can eliminate many security threats. These threats...
## 6.1 Communication Channel Security	## 6.1 Communication Channel Security SAP S/4 HANA uses several protocols for communication to internal and external applications. These can be SAP systems or third-party systems. The following protocols are supported: - HTTPS HTTP connections are protected by the Transport Layer Security (TLS) protocol. This protocol ...
## 6.2 Network Security	## 6.2 Network Security ## Network SAP S/4HANA is based on ABAP Platform technology. Therefore, for information about network security, see the respective sections in the ABAP Platform Security Guide. This includes information on using firewall systems for access control and using network segmentation. Go to https:/ /h...
## 6.3 Communication Destinations	## 6.3 Communication Destinations The use of communication destination is application-specific. Therefore please check the application-specific chapters for details. In this context please note that users and authorizations should be used with specific care, as the use of users and authorizations in an irresponsible ma...
## 7 ICF and Session Security	## 7 ICF and Session Security ## Internet Communication Framework (ICF) Services You should handle Internet Communication Framework (ICF) services in a restrictive manner in order to minimize the attack surface on the web. ##  Note As a general rule you should only activate those ICF services that are needed for the a...
## 8 File System Access Security	## 8 File System Access Security ## More Information For detailed information about data storage security, see the ABAP Platform Security Guide. ## Using Logical Paths and File Names to Protect Access Some applications in SAP S/4HANA save data in files in the file system. Therefore, it is important to explicitly provid...
## 9 Virus Scanning	## 9 Virus Scanning ## Basic Concepts We recommend installing and running a VSI 2.x-compliant virus scanner in your landscape. The SAP S/4HANA code calls this scanner using a dedicated interface during different stages of processing - during upload, download, and passage through the Gateway, and so on. You can customiz...
## 9.1 General Recommendations for Virus Scan Profiles	## 9.1 General Recommendations for Virus Scan Profiles We recommend that you enable all pre-delivered virus scan profiles. The decision to deactivate a scan profile requires a security risk assessment. ## Customer Profiles You should set up the following customer profiles: \| Name \| Description \| \|---...
## 9.2 Virus Scanning in File Uploads	## 9.2 Virus Scanning in File Uploads ## Example The system allows uploading of files. For example, users can add an attachment to business documents. Also, you can upload template files, such as e-mail HTML templates, which can be used to render data on a UI. Once uploaded into SAP S/4HANA, such documents may be displ...
## 9.3 Scan Profiles for File Downloads	## 9.3 Scan Profiles for File Downloads The following pre-delivered profiles are used for download-time scanning: - /SCET/GUI\_DOWNLOAD - /SIHTTP/HTTP\_DOWNLOAD - /SOAP\_CORE/WS\_SEND Scanning files on download as well as upload offers additional security benefits. Typically, the virus signature database will have been...
## 9.4 Further Protection Against Active Content	## 9.4 Further Protection Against Active Content ## Lines of Defense There are at least two lines of defense against active content. The first is performing virus scanning in order to avoid uploading malicious content in the first place. The second line of defense is SAP WebDispatcher. An alternative is the Internet Co...
## 10 Additional System Hardening Activities	## 10 Additional System Hardening Activities ## Click-Jacking Protection Click-jacking is an attack type where an attacker tries to hijack the clicks of an authenticated user in order to trigger malicious actions. This attack is based on framing the attacked page into an attacker-controlled enclosing page. SAP S/4HANA ...
## 11 Data Protection and Privacy	## 11 Data Protection and Privacy ## Use Data protection is associated with numerous legal requirements and privacy concerns. In addition to compliance with general data protection acts, it is necessary to consider compliance with industry-specific legislation in different countries. This section describes the specific...
## 11.1 Read Access Logging	## 11.1 Read Access Logging ## Use Read access to personal data is partially based on legislation, and it is subject to logging functionality. The Read Access Logging (RAL) component can be used to monitor and log read access to data and provide information such as which business users accessed personal data (for examp...
## 11.2 Deletion of Personal Data	## 11.2 Deletion of Personal Data Personal data in a system can be blocked as soon as the business activities for which this data is needed are completed and the residence time for the data has elapsed. After this time, only users who are assigned additional authorizations can access the data. When the retention period...
## 11.3 Information Retrieval	## 11.3 Information Retrieval Data subjects have the right to get information regarding their personal data undergoing processing, including the reason (purpose) for processing. The Information Retrieval Framework component can be used to carry out a cross-application search for personal data of a specified data subjec...
## 11.4 Consent Administration	## 11.4 Consent Administration ## Use Any personal data collected or processed must be linked to a specific, predefined purpose, such as the fulfillment of a contract or legal obligation. If you must obtain consent from the data subject to use their personal data, this consent data can be stored in the SAP system as co...
## 12 SAP S/4HANA Cross Application Infrastructure	## 12 SAP S/4HANA Cross Application Infrastructure
## 12.1 Data Security in SAP ILM	## 12.1 Data Security in SAP ILM SAP ILM offers options for protecting data security from the archiving of data up to its storage and destruction. All system connections and ILM functions have authorization protection. ## Related Information Data Security in SAP ILM System Connections [page 37] Users and Authorizations...
## 12.1.1 Data Security in SAP ILM System Connections	## 12.1.1 Data Security in SAP ILM System Connections ## System Landscape Components The SAP ILM system landscape includes the following main components: - Application system (AS ABAP) - WebDAV server on which ILM stores are set up - System on which the service for the control of ILM stores runs Since two different se...
## 12.1.2 Users and Authorizations in SAP ILM	## 12.1.2 Users and Authorizations in SAP ILM ## User To make SAP ILM available, you need users for the communication between the participating systems (using HTTP connections). For more information, see Data Security in SAP ILM System Connections under SAP Information Lifecycle Management. ## Authorizations SAP deliv...
## 12.1.3 Security of Stored Data in SAP ILM	## 12.1.3 Security of Stored Data in SAP ILM ## Security of Archived Data in the File System When storing archived data in the file system, you have read and write access to the file system with the technical system user of the SAP system. The system temporarily moves the archive files to the file system and then dele...
## 12.1.4 Logs in SAP ILM	## 12.1.4 Logs in SAP ILM In SAP ILM , logging depends on the service you use to control the stores. \| Service Used \| Type of Log File \| Server \| Description ...
## 12.2 Payment Card Security	## 12.2 Payment Card Security
## 12.2.1 Before You Start	## 12.2.1 Before You Start Since the measures described in this guideline for security in the use and administration of payment cards apply in various applications, see the security guides for those particular applications. The most important SAP Notes that apply to secure handling of payment card data are shown in th...
## 12.2.2 Authorizations	## 12.2.2 Authorizations The functions for secure handling of payment cards use the authorization concept provided by ABAP platform. Therefore, the recommendations and guidelines for authorizations as described in the ABAP Platform Security Guide also apply to the secure handling of payment cards. The ABAP platform au...
## 12.2.3 Data Storage Security	## 12.2.3 Data Storage Security ## Use Since payment card data is needed by many different applications for operational processes, the data is stored on the database. If you choose the security level Masked Display, and Encrypted When Saved , the system stores payment card numbers in encrypted form on the database in ...
## 12.2.4 Setting Up Encryption Software	## 12.2.4 Setting Up Encryption Software To be able to encrypt payment card data in the system, you must install the function package SAPCRYPTOLIB. The function package SAPCRYPTOLIB contains the functions necessary for encryption. To execute the encryption software, you have to make general settings in Customizing for...
## 12.2.5 Making Settings for Payment Card Security	## 12.2.5 Making Settings for Payment Card Security You make settings for payment card security in Customizing for Cross-Application Components under Payment Cards Basic Settings Make Security Settings for Payment Cards . The following explanations refer to the settings there. ## Security Level You can select from the...
## 12.2.6 Relevant SSF Applications	## 12.2.6 Relevant SSF Applications For encryption and decryption using the SSF Framework, the applications communicate using an SSF application. The keys (PSEs) used for encryption and decryption are generated for each SSF application. If you have not activated key replacement, then, for technical reasons, various SS...
## 12.2.7 Generating Keys	## 12.2.7 Generating Keys The generation of the keys (PSEs) used for encryption and decryption differs depending on the SSF application: ## · SSF Application *PAYCRV To generate a key version, on the SAP Easy Access screen, choose Cross-Application Components Security of Payment Card Data Encryption of Payment Cards A...
## 12.2.8 Migration of Payment Card Data Stored in Unencrypted Form	## 12.2.8 Migration of Payment Card Data Stored in Unencrypted Form You can use several migration programs to migrate payment card data stored in unencrypted form to encrypted payment card data. These programs comply with the naming convention RCCSEC\_MIGRATION\_*. For information on which program you can use for your...
## 12.2.9 Migration of Payment Card Data on SAP Business Partner	## 12.2.9 Migration of Payment Card Data on SAP Business Partner The following section is relevant for you only if you use the SAP business partner. For the SAP business partner in S/4HANA systems to support encrypted storage of payment card data, a one-time data migration is required. Before this migration, the syste...
## 12.2.10 Migration to SSF Application PAYCRV	## 12.2.10 Migration to SSF Application PAYCRV If you already encrypted credit card data in the system (using the SSF applications PAYCRD or CCARD), you can migrate this data to the SSF application PAYCRV. As a result, the system then also replaces the keys for this data on a periodic basis. Start the migration on the...
## 12.2.11 Migration to Current Key Version	## 12.2.11 Migration to Current Key Version Once you have generated a new key version, you can migrate the data, which was encrypted and stored under an older key version, to the current key version. During this process, the system decrypts the data record with the older key version, encrypts the data with the current...
## 12.2.12 Deleting a Key Version	## 12.2.12 Deleting a Key Version Once the data of an old key version has been migrated completely to the current key version, the old key version receives the status deletable . T o ensure the utmost security, the earliest the key version can actually be deleted is after an additional waiting period of 90 days after ...
## 12.2.13 Security-Relevant Logging and Tracing	## 12.2.13 Security-Relevant Logging and Tracing ## Use You can have the system log users' access to unmasked payment card data. In Customizing, choose the setting Access Log: Logs for Unmasked Display (see Making Settings for Payment Card Security [page 44]). The system updates the log on database table CCSEC\_LOG. Y...
## 12.2.14 Recommended Implementation Steps	## 12.2.14 Recommended Implementation Steps The following recommended implementation steps differ according to which of the following situations apply to you: - You did not yet set a security level. - You are already using the security level for saving payment card numbers in encrypted form, and you now want to implem...
## 12.3 Data Security in Behavioral Insights	## 12.3 Data Security in Behavioral Insights
## 12.3.1 Roles and Authorizations	## 12.3.1 Roles and Authorizations This section describes the use of roles and authorizations in SAP S/4HANA for behavioral insights (abbreviated to: Behavioral Insights).