eCATT Security Guide
This guide does not replace the daily operations handbook that we recommend customers to create for their specific productive operations.
Target Audience
● Technical consultants
● System administrators
Why Is Security Necessary?
Your SAP Systems contain a wealth of sensitive data – data that is essential for the day-to-day running of your business, data that you are required by law to protect from unauthorized access, data that you would not want your competitors or a disgruntled employee to see, much less be able to compromise in some way. Security is an issue that SAP takes seriously, providing an extensive authorization concept to protect transactions and data from unwanted access.
About This Document
The security guide provides an overview of the security-relevant information that applies to eCATT.
The aim of this guide is to help you make informed choices about your security policy in your testing environment by explaining the authorizations required for different kinds of eCATT users. It also explains the security features implemented to protect your systems from unwanted GUI scripting access.
Overview of the Main Sections
The Security Guide comprises the following main sections:
This section contains information about the client settings that you must specify in each client in which you want to run CATT procedures or eCATT test scripts.
This section provides an overview of the technical components that can be used in eCATT test scenarios.
This section provides an overview of the authorization concept that applies to eCATT.
● Network and Communication Security
This section provides an overview of the communication paths used by eCATT and how to set up Trusted RFC.
● Security for Additional Applications
This section provides security information that applies to third-party or additional applications that are used with eCATT.
● Other Security-Relevant Information
This section contains information regarding GUI Scripting access.