Implementing NIST Cyber Security Framework Using COBIT 2019 — Lesson 2: Current Profile, Risk Priorities, COBIT Objectives, and Control Mapping

Learning Objectives

• Explain the roles, information, criteria, dependencies, and decision points governing current profile and risk priorities.
• Implement or assess COBIT objectives, control mapping, and responsibility assignment using controlled evidence and acceptance criteria.
• Evaluate the condition where a control passes a basic check but control mapping fails because COBIT objectives data, criteria, or dependency assumptions differ and select a proportionate corrective response.

Detailed Topics

• current profile applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• risk priorities applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• COBIT objectives applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• control mapping applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• responsibility assignment applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.

Instructor Demonstration

The instructor traces a governance team translating NIST cybersecurity outcomes into COBIT responsibilities, processes, measures, evidence, and executive reporting. The walkthrough connects frameworks, processes, tools, decisions, and evidence captured in the NIST-to-COBIT mapping, implementation backlog, control metrics, and assurance report. It also tests the exception where a control passes a basic check but control mapping fails because COBIT objectives data, criteria, or dependency assumptions differ.

Hands-On Exercise

Complete a controlled ISACA-aligned exercise covering Current Profile, Risk Priorities, COBIT Objectives, and Control Mapping and preserve the verified result in the NIST-to-COBIT mapping, implementation backlog, control metrics, and assurance report.

1. Confirm scope, roles, criteria, prerequisites, information sources, dependencies, and acceptance conditions.
2. Execute the governance, risk, audit, security, data, cloud, or technology workflow while recording decisions and evidence.
3. Test normal behavior, one boundary condition, and the stated exception using a controlled scenario.
4. Document findings, corrections, ownership, retest criteria, communication, and operational handover.

Scenario Analysis

• Identify which role, process, objective, control, data source, or decision most strongly influences current profile.
• Compare two defensible responses and explain governance, risk, audit, security, privacy, operational, and business trade-offs.
• Determine how the NIST-to-COBIT mapping, implementation backlog, control metrics, and assurance report should be approved, retained, reviewed, retested, and updated.

Troubleshooting Guidance

Start where expected behavior first differs from the observed result. Check scope, criteria, ownership, data quality, process sequence, policy alignment, version compatibility, dependencies, status, and evidence separately. Treat “a control passes a basic check but control mapping fails because COBIT objectives data, criteria, or dependency assumptions differ” as a hypothesis until records, interviews, configurations, calculations, and retest outcomes confirm the cause.

Validation Checklist

• Required roles, processes, criteria, controls, information, approvals, and dependencies are present.
• The NIST-to-COBIT mapping, implementation backlog, control metrics, and assurance report connects each conclusion to objective, reviewable evidence.
• Normal processing, a boundary condition, dependency behavior, and the stated exception were tested.
• Corrections, ownership, retest criteria, documentation, communication, and operational handover are complete.

Lesson Outcome

Learners can apply Current Profile, Risk Priorities, COBIT Objectives, and Control Mapping, explain the resulting governance, risk, audit, security, data, or operational behavior, and defend the outcome through the NIST-to-COBIT mapping, implementation backlog, control metrics, and assurance report.