Active

API Continuous Improvement

The organization shall drive ongoing enhancement of API access control through a continuous improvement process. The process shall use inputs from API reviews, incident analysis, and best practice benchmarking to identify, implement, and measure improvements.

Requirement ID
IAM-007-R010
Parent Control
Domain Code

Requirement Details & Guidance

IAM-007-R010 · IAM-007
Why This Requirement Exists

This requirement exists to improve API access control using reviews, incidents, and benchmarking and to ensure identity and access decisions are controlled, traceable, and aligned with business and security needs.

Implementation Guidance

Define and document the process for improve API access control using reviews, incidents, and benchmarking. Establish accountable owners, required inputs and outputs, approval or validation points, risk-based criteria, review frequency, exception handling, monitoring, and evidence requirements. Integrate the process with authoritative identity sources and relevant HR, application, infrastructure, security, and compliance workflows. Retain records sufficient to demonstrate operation.

Practical Application & Audit Readiness

IAM-007-R010 · Field Guidance

Business Examples

    Common Audit Findings

      Common Mistakes

        Best Practices & Ownership

        IAM-007 · Recommended Approach

        Recommended Practices

          Typical Owner

          Cross-Mapped Regulatory Frameworks

          Harmonized Control Mappings
          FRAMEWORK CODE FRAMEWORK NAME & DETAILS FAMILY / CATEGORY VERSION ACTION
          ISO27001 ISO/IEC 27001 ISO/IEC 27001 specifies auditable requirements for... Clause: 10.1 – Continual improvement
          ISO
          Standard
          v2022 View →
          RBI-CSF RBI Cyber Security Framework / Master Directions RBI cyber-security requirements and directions set... Clause: 8) User Access Control / Management – 8.4 Centralised authentication/authorization, strong passwords, MFA, least privilege and segregation of duties; 8) User Access Control / Management – 8.2 Protection of customer access credentials, authentication information and tokens
          India
          Regulation
          vLatest View →
          SEBI-CSCRF SEBI Cyber Security & Cyber Resilience Framework SEBI’s Cybersecurity and Cyber Resilience Framewor... Clause: 3.1 PR.AA: Identity Management, Authentication, and Access Control
          India
          Regulation
          vLatest View →
          DORA Digital Operational Resilience Act The EU Digital Operational Resilience Act establis... Clause: Article 9(4)(d) – Strong authentication, cryptographic keys and encryption
          EU
          Regulation
          vCurrent View →
          ISO27002 ISO/IEC 27002 ISO/IEC 27002 is a guidance standard containing a... Clause: 5.15 – Access control
          ISO
          Standard
          v2022 View →
          NIS2 NIS2 Directive The NIS2 Directive establishes EU-wide cybersecuri... Clause: Article 21(2)(i) – Human resources security, access control policies and asset management
          EU
          Directive
          vCurrent View →
          COBIT2019 COBIT COBIT is an enterprise governance and management f... Clause: 4.4 – Deliver, Service and Support (DSS) > DSS06 – Managed Business Process Controls > DSS06.03 – Manage roles, responsibilities, access privileges and levels 4.4 – Deliver, Service and Support (DSS) > DSS05 – Managed Security Services > DSS05.07 – Manage vulnerabilities and monitor the infrastructure for
          COBIT
          Governance Framework
          v2019 View →
          NIST-CSF NIST Cybersecurity Framework (CSF) The NIST Cybersecurity Framework provides high-lev... Clause: PR.AA – Identity Management, Authentication, and Access Control | PR.AA-01 – Identities and credentials for authorized users, services, and hardware are managed by the organization PR.AA – Identity Management, Authentication, and Access Control | PR.AA-05 – Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties
          NIST
          Framework
          v2 View →
          NIST80053 NIST SP 800-53 NIST SP 800-53 Rev. 5 presents control families, i... Clause: 3.7 – IDENTIFICATION AND AUTHENTICATION; IA-2 – IDENTIFICATION AND AUTHENTICATION (ORGANIZATIONAL USERS), IA-9 – SERVICE IDENTIFICATION AND AUTHENTICATION
          NIST
          Control Catalog
          vRev. 5 View →
          NPCI-ISR NPCI Information Security Requirements NPCI information-security requirements define cont... Clause: Security Measures / Controls; Identity and Access Management
          India
          Standard
          vLatest View →
          SOC2 SOC 2 Trust Services Criteria SOC 2 is an independent examination and reporting... Clause: CC6.1 – Logical and Physical Access Controls – The entity implements logical access security software, infrastructure, and architectures over protected information assets to protect them from security events to meet the entity's objectives. CC6.3 – Logical and Physical Access Controls – The entity authorizes, modifies, or removes access to data, software, functions, and other protected information assets based on roles, responsibilities, or the system design and changes, giving consideration to the concepts of least privilege and segregation of duties, to meet the entity’s objectives. CC4.1 – Monitoring of Controls – COSO Principle 16: The entity selects, develops, and performs ongoing and/or separate evaluations to ascertain whether the components of internal control are present and functioning. CC4.2 – Monitoring of Controls – COSO Principle 17: The entity evaluates and communicates internal control deficiencies in a timely manner to those parties responsible for taking corrective action, including senior management and the board of directors, as appropriate.
          AICPA
          Audit Framework
          vLatest View →

          Parent Domain Context

          Governance Domain Baseline
          Domain Name:
          Identity & Access Management (IAM)
          Purpose:
          To ensure that only authorized users have appropriate access to systems and data.
          Scope:
          Enterprise

          Parent Control Context

          Control Baseline
          Control Name:
          Access Control for APIs (IAM-007)
          Summary:
          Establishes comprehensive API access controls including authentication, authorization, rate limiting, input validation, token management, and monitoring to protect APIs from unauthorized access and abuse.
          Business Description:
          Implement robust access controls for APIs to protect them from unauthorized access.