CSI tools Facebook CSI tools Twitter CSI tools LinkedIn CSI tools Instagram
  • Home
  • Newsroom
    • Awards
    • Events
    • Press Releases
    • Publications
  • Software
    • By Solution
      1. Access Risk Management
      2. Access Request Management
      3. Privileged Access Management
      4. Access Role Management
      5. SAP License Audit
      6. Mass User Maintenance
    • Tools
      1. CSI Authorization Auditor
      2. CSI Automated Request Engine
      3. CSI Emergency Request
      4. CSI Role Build & Manage
      5. CSI Mass User Maintenance
      6. CSI Integrate & Collaborate
    • Pathlock
    • Legacy Tools
    • Pathlock Cloud: The Successor of CSI tools
  • Customer Center
  • Community
    • CSI tools Forum
    • Meta's Blog
    • Tech Updates
    • Training
  • About
    • Contact
    • Jobs
    • Partners
      • Become a Partner
    • References
    • Testimonials
    • Sustainability
  • Login
  • You are here:  
  • Home
  • Meta's Blog Home
  • SAP special users

SAP Special Users

SAP NetWeaver AS ABAP creates the standard users SAP*, DDIC, EARLYWATCH, TMSADM, and SAPCPIC during the installation process. The standard users are protected by defaults passwords. Nowadays, most companies are aware of this and will change this default password(s) and implement security procedures for these users.

SAP recommends to take the following action securing the users:

  • Maintain an overview of the clients that you have and make sure that no unknown clients exist.
  • Make sure that SAP* exists and has been deactivated in all clients.
  • Make sure that the default passwords for SAP*, DDIC, and EARLYWATCH have been changed.
  • Make sure that these users belong to the group SUPER in all clients.
  • Lock the users SAP*, DDIC, and EARLYWATCH. Unlock them only when necessary.
  • Delete SAPCPIC if you do not need it. At least make sure that you have changed the default password for SAPCPIC.
  • Change the default password of TMSADM.
    for more information, see Changing the Password of User TMSADM.

I agree these actions need to be taken to provide a minimum level of security for these users. But is this really enough?

I would recommend to spend some time analyzing the usage of these users. This can be done via additional security audit software and/or combined with the security audit log.
You might be surprised with the results. In many cases we could see that a SAP standard user was being used for logging on to the system via interfaces or running background jobs that nobody knew of.

Then the fun part starts: answering the "what" and "why" questions and clean up/document everything......
Be warned, this might take some time!
Good Luck!

(C) Meta Hoetjes 2014
CSI Authorization Auditor and CSI Role Build and Manage are registered trademarks by CSI tools bvba
www.csi-tools.com

Get in touch

Pathlock Benelux
Support Direct
Link to the support portal https://support.pathlock.com

To gain access to the new support portal, please contact us at customersupport@pathlock.com

Tel. +32 16 308 008

Address
Kempische Steenweg 303/200
B-3500 Hasselt, Belgium

Via phone
Tel: +32 16 308 000

Last Updates

  • Pathlock Cloud: The Successor of CSI tools
  • Pathlock named Market Leader for Zero Trust by Cyber Defense Magazine

Solutions

  • SoD and Risk analysis - CSI Authorization Auditor
  • Compliant Provisioning - CSI Automated Request Engine
  • Emergency Access Management - CSI Emergency Request
  • Compliant Role and Mass User Management - CSI Role Build & Manage
  • Extract SAP data - CSI Data Xtractor
  • CSI Integrate & Collaborate

©1997-2025 Pathlock Benelux. All rights reserved. - Privacy Policy  - Cookie Policy - Code of Ethical Conduct - Sitemap