Home > SAP Tips > Basis administration > R/3 audit review questions
SAP Tips:
EMAIL THIS
 TIPS & NEWSLETTERS TOPICS 

BASIS ADMINISTRATION

R/3 audit review questions


Amy Lambermont
06.14.2002
Rating: -3.35- (out of 5)


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


Here is a list of items most commonly reviewed by internal/external auditors when reviewing your R/3 system. It is always a good idea to review this list a couple times a year and to take the appropriate steps to tighten your security. If requested I can e-mail this to you in Word format.

Review the following:

* System security file parameters (TU02) (e.g. password length/format, forced password sessions, user failures to end session etc.) have been set to ensure confidentiality and integrity of password. Security-Parameter-Settings-Documentation.doc

* Setup and modification of user master records follows a specific procedure and is properly approved by management.

* Setup and modification of authorizations and profiles follows a specific procedure and is performed by someone independent of the person responsible for user master record maintenance.

* An appropriate naming convention for profiles, authorizations and authorization objects has been developed to help security maintenance and to comply with required SAP R/3 naming conventions.

* A user master record is created for each user defining a user ID and password. Each user is assigned to a user group, in the user master record, commensurate with their job responsibilities.

* Check objects (SU24) have been assigned to key transactions) to restrict access to those transaction.

* Authorization objects and authorizations have been assigned to users based on their job responsibilities.

* Authorization objects and authorizations have been assigned to users ensuring segregation of duties.

* Users can maintain only system tables commensurate with their job responsibilities.

* Validity periods are set for user master records assigned to temporary staff.

* All in-house developed programs contain authority check statements to ensure that access to the programs are properly secure.

* Select a sample of:

* Changes to user master records, profiles and authorizations and ensure the changes were properly approved. (The changes can be viewed with transaction (SECR).

* Ensure that security administration is properly segregated. At a minimum there should be separate administrators responsible for:
- User master maintenance. (This process can be further segregated by user group.)
- User profile development and profile activation. (These processes can be further segregated.)

* Verify that a naming convention has been developed for profiles, authorizations and in-house developed authorization objects to ensure:
- They can be easily managed.
- They will not be overwritten by a subsequent release upgrade (for Release 2.2 should begin with Y_ or Z_ and for Release 3.0 by Z_ only.)

* Assess through audit information system (SECR) or through a review of table USR02, whether user master records have been properly established and in particular:
* The SAP_ALL profile is not assigned to any user master records.
* The SAP_NEW profile is not signed to any user master records. Verify that procedures exist for assigning new authorization objects from this profile to users following installation of new SAP releases.

* Assess and review of the use of the authorization object S_TABU_DIS and review of table authorization classes (TDDAT) whether:
- All system tables are assigned an appropriate authorization class.
- Users are assigned system table maintenance access (Through S_TABU_DIS) based on authorization classes commensurate with their job responsibilities.

* Asses and review of the use of the authorization objects S_Program and S_Editor and the review of program classes (TRDIR) whether:
- All programs are assigned the appropriate program class.
- Users are assigned program classes commensurate with their job responsibilities.

* Ensure through a review of a sample of:
- In-house developed programs that the program, code either:
- Contains an Authority-Check statement referring to an appropriate authorization object and valid set of values; or
- Contains a program Include statement, where the referred program contains an Authority-Check statement referring to an appropriate authorization object and valid set of values.


Rate this Tip
To rate tips, you must be a member of SearchSAP.com.
Register now to start rating these tips. Log in if you are already a member.


Submit a Tip




Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


RELATED CONTENT
Basis administration
Select Text fields: Case-insensitive
Finding BADIs you can use
Easier maintenance of output types, procedures, conditions, etc.
Is this the quickest way to find a BADI?
Top 10 SAP tips of 2007
Dealing with backup server instability
SAP security audit log setup
Do not use SAP GUI with Internet Explorer 7 Beta
How to reinstall the Support Package Manager from the command line in SAP Basis
Display locked and unlocked SAP transactions

SAP Basis
Error when clicking the SAP GUI logon button
The difference between an SAP system and a non-SAP system
Becoming an SAP administrator: The self-study route
Basis consultant wants to learn NetWeaver Portal
SAP administration information for a Basis interview
Quiz: SAP ABAP development
What does the Parameter tab mean in SU01
Changing a customer message priority level after it's sent
Basis administration info in preparation for an interview
Easier maintenance of output types, procedures, conditions, etc.
SAP Basis Research

SAP security
The difference between an SAP system and a non-SAP system
SAP administration information for a Basis interview
Quiz: SAP ABAP development
Restricting sales document assignments by sales area
Authorization objects with a value of single/double quote marks
Error logging in using a reference ID
Easier maintenance of output types, procedures, conditions, etc.
Security risk: Users able to see data from other companies
Assigning roles to all users in a group
On The Spot: Mario Linkies on SAP security

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
Basis  (SearchSAP.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary

DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

HomeNewsTopicsBlogsTipsAsk the ExpertsMultimediaWhite PapersProducts
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Reprints  |  Site Map




All Rights Reserved, Copyright 2000 - 2008, TechTarget | Read our Privacy Policy
SearchSAP.com is a search service provided by TechTarget and is completely
independent of and not affiliated with SAP AG.
  TechTarget - The IT Media ROI Experts