Sekit CSF · Application Security · Policy
RCF-0136API security
Security requirements for all application programming interfaces are formally defined and documented
Mapping at a glance
RCF-0136API securityApplication Security · Policy
RCF-0136 maps to 5 controls across the published frameworks. Open in the full graph →
Maps to ISO/IEC 27001:2022 · Annex A controls
Curated mapping with the reasoning, not just the codes.
A.5.1Policies for information securitysupportsAmong A.5.1's topic-specific policies, Sekit's API security policy documents the authentication, authorisation and data-handling requirements every company API must meet.A.8.26Application security requirementssupportsThis policy facet documents the authentication, authorization and data-handling requirements every API must meet, a direct instance of A.8.26's application security requirements.
Maps to NIST CSF 2.0
Curated mapping with the reasoning, not just the codes.
PR.AA-05Access permissions managedPR.PS-01Configuration management appliedPR.PS-04Logs generated for monitoring
Evidence that proves this control
What an auditor, or Sekit's evidence engine, asks for.
Application security testing evidence
The proof that code and applications are automatically scanned for flaws (SAST/DAST), including dependencies and APIs.
From the Sekit evidence catalog
This topic through the other lenses
All Application Security controls
Ask Sekura: “What evidence proves RCF-0136?”
Connect your AI · free MCP
https://sekit.ai/api/mcp/crosswalk- In Claude or ChatGPT, add a custom connector and paste this URL.
- Sign in with your email to finish. Free, read-only, no organization required.