ABAP code is the custom application logic used to extend or modify SAP systems. Because it can change business behaviour, it must be governed like production software. Security teams should review it for unsafe logic, unauthorized access paths, and controls that prevent unapproved changes from reaching live environments.
What ABAP Code Is Used For
ABAP is SAP’s application programming language for extending standard ERP behaviour, automating business processes, and customising workflows, validations, reports, and integrations. Because ABAP can alter how core transactions execute, even small code changes can affect permissions, data handling, and downstream business outcomes.
In practice, ABAP code sits close to production control planes. That makes the language less about syntax alone and more about the trust placed in custom logic, transport handling, and the review discipline around every change that moves from development into live SAP environments.
Why ABAP Needs Security Review
ABAP is security-relevant because custom code can introduce new access paths, bypass intended checks, or expose sensitive business data through reports, RFCs, exits, or custom transactions. A routine functional enhancement can become a control gap if it assumes callers are trusted or if it reimplements authorisation logic inconsistently.
Secure ABAP development is therefore partly about secure design and partly about code governance. The same system may contain standard SAP controls and custom code that changes the effective security posture, so the code itself has to be treated as part of the attack surface.
That is why organisations review ABAP for direct object access, unsafe dynamic statements, hard-coded privileges, insecure input handling, and logic that changes approval or segregation-of-duties outcomes. These issues can be subtle because the code may behave correctly in testing while still weakening production controls.
How Organisations Govern ABAP Changes
ABAP governance is usually a change-control problem as much as a development problem. Organisations need clear ownership for code, strong transport approval, and separation between development, testing, and production so that custom logic cannot be promoted informally or modified outside normal release paths.
Review should cover both the source code and the surrounding process. That includes who can create or change code, who can move transports, how emergency fixes are handled, and whether custom objects have an accountable business owner as well as a technical owner.
Effective governance also means understanding the business risk of each custom object. A harmless-looking report may only retrieve data, while a custom transaction may update master data, approve payments, or surface information that standard roles were never meant to expose.
Secure Development and Maintenance Practices
ABAP maintenance should follow the same secure engineering discipline applied to other production software, with secure coding standards, peer review, test coverage, and traceable promotion into production. The goal is not only to stop defects, but to stop security-relevant logic from becoming embedded in business workflows.
Teams should pay close attention to custom authorisation checks, input validation, error handling, logging, and use of privileged statements. When ABAP code calls external services or reads sensitive tables, the implementation needs to be explicit about trust boundaries and data minimisation.
Long-lived custom code also needs periodic re-review. Business processes change, standard SAP functionality evolves, and old ABAP routines can become obsolete controls that still run in production but no longer match current policy or entitlement models.
Risk and Threat Considerations
ABAP code creates security risk when custom logic weakens SAP controls, exposes sensitive business data, or gives attackers a path to modify transactions, extract records, or manipulate approvals. The danger is not limited to bugs, it includes trusted business logic behaving in ways the organisation did not intend.
Failure mechanism: A developer or attacker with code-change access can introduce logic that bypasses checks, embeds hidden backdoors, or silently broadens data access, while transport or review weaknesses let that logic reach production.
Impact: The result can be fraud, unauthorised disclosure, business-process manipulation, and persistent control failure inside a system that stakeholders assume is governed.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, CIS Controls v8 and OWASP ASVS set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | SA-11 — Developer Testing and Evaluation | ABAP custom logic needs secure review and testing before production use. |
| CM-3 — Configuration Change Control | ABAP transports and code changes must be controlled before they alter live SAP behaviour. | |
| AC-6 — Least Privilege | ABAP often determines who can read, update, or bypass business data and transactions. | |
| Recommendation — Review custom ABAP logic for security defects before promoting it to production. Require formal approval for ABAP changes that affect production systems. Constrain ABAP-related access so code and operators have only the privileges they need. | ||
| CIS Controls v8 | CIS-4 — Secure Configuration of Enterprise Assets and Software | Custom ABAP is software that must be secured, reviewed, and maintained as part of the estate. |
| Recommendation — Harden and review ABAP changes as part of software configuration management. | ||
| OWASP ASVS | V15 — Secure Coding and Architecture | ABAP code can introduce insecure logic, weak validation, and unsafe access patterns. |
| Recommendation — Apply secure coding review to ABAP changes that influence business logic and access decisions. | ||
Practitioner Guidance
Why practitioners should care: Treat ABAP as production-critical logic, not as a purely technical customisation layer. The most important control question is whether a code change alters access, approval, data visibility, or process integrity.
Governance implication: Make code ownership, transport approval, and emergency-change handling explicit, and ensure reviews focus on security effects as well as functional correctness. That keeps custom SAP behaviour aligned with the controls the business thinks it has.
Practitioner takeaway: If ABAP can change business behaviour, it must be reviewed and governed with the same seriousness as any other code that can affect production trust.
Related resources from NHI Mgmt Group
- Why do unmanaged ABAP code and transports create governance risk in SAP environments?
- Why is hardcoding credentials into source code so dangerous?
- What is the difference between code scanning and runtime identity monitoring?
- What is the difference between scanning AI-generated code and governing AI agent identity?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 1, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org