NIST Cybersecurity Framework 2.0
NIST CSF 2.0 organises cybersecurity risk outcomes into six functions: Govern, Identify, Protect, Detect, Respond and Recover. Apps Intellect can use these functions to structure its programme, identify gaps and communicate risk management activities. A CSF profile should describe the current and target outcomes relevant to the organisation; referencing the framework does not mean every outcome has been achieved.
Cloud Security Alliance Cloud Controls Matrix
The CSA Cloud Controls Matrix (CCM) is a cloud-focused cybersecurity control framework. It can be used to examine cloud governance, infrastructure, application, data and supplier-related risks. Any mapping should identify the applicable cloud service model, shared-responsibility boundaries, control owner and evidence source. A completed mapping is an assessment artefact, not by itself an independent assurance opinion.
CSA STAR and CAIQ
CSA STAR provides a cloud security assurance programme with different levels and assessment routes. A Level 1 self-assessment is based on provider-submitted information and should be described as a self-assessment if published. It must not be presented as an independent audit, certification or proof that all controls are effective. The Consensus Assessments Initiative Questionnaire (CAIQ) can be used to organise cloud security questions and responses.
OWASP application security guidance
OWASP resources, including the OWASP Top 10 and Application Security Verification Standard, can inform application threat modelling, secure design, testing and remediation. The relevant version and testing scope should be recorded. Use of OWASP guidance does not constitute an OWASP certification.
Privacy and regulatory obligations
Privacy obligations must be assessed against actual processing activities, locations, parties and data subjects. GDPR applicability and roles should be determined for each relevant activity; a general statement that a service is “GDPR compliant” should not replace this analysis. Contractual terms, data processing agreements, international transfer mechanisms and subprocessor information should be reviewed where applicable.
How mappings will be maintained
- Record the framework and version used.
- Map each requirement to an internal policy, process or technical control.
- Identify the accountable owner and evidence reference.
- Record status, gap, risk treatment and target date.
- Review mappings when products, infrastructure, legal obligations or framework versions change.
Customer-specific requirements
Airline and enterprise customers may use their own questionnaires, procurement standards or contractual security schedules. Responses should be evidence-based, approved by the relevant owner and limited to the service and period being assessed. Use the customer security information request page to begin an assurance discussion.
Related information
Read the Security overview, Data protection overview or request security information.
