CYBERJA · PRACTICE GUIDEFrom business scope to audit readiness
A 20–25 minute video walkthrough and self-paced practice exercise. All records, names and test results are fictional. Use a separate browser profile if you have existing programme records.
Open the tool · Open this file in a browser or print it to PDF.
Opening · 0:00
Say: A customer asks for evidence that your company manages information security risks. We will turn scattered policies, settings and logs into a programme management can act on. Follow one finding: two production administrators can sign in without MFA.
1. Define the business & scope · 0:45
Open Document business context. Enter HarbourPay Services Ltd. as a fictional cloud-hosted payment operations software company with support and engineering in Kingston, Jamaica, serving Jamaica and UK customers. Confirm hosting locations, processing roles and applicable obligations during discovery.
Scope the customer portal, production releases, privileged access, customer support, monitoring and recovery. Exclude the public marketing site from the portal scope but retain any data or login interface. The external processor owns its environment. Keep the integration, contracts and supplier assurance in scope.
Processes: onboarding, reconciliation, support, releases and incident response. Systems: Azure, Entra ID, managed database, GitHub deployment workflows and service desk. Data: business contacts, transaction references, reconciliation reports and support records. Payment entry is assumed processor-hosted and must be verified separately.
The cloud provider operates managed infrastructure. HarbourPay owns tenant configuration, identity and application controls. The processor operates payment entry and HarbourPay owns integration and supplier oversight. COO sponsors and approves. GRC Lead coordinates. Engineering and IT Operations own controls. Security Assurance reviews evidence independently.
Goal: enterprise onboarding readiness and an evidence-backed investment plan. Use 4 December 2026 or a comparable future handoff date. Sources: fictional sponsor interview, inventory and integration diagram. Open questions: processor flow, contract wording and privileged inventory.
Say: Scope follows the service and its dependencies. Save the profile and point to the boundary, supplier interface and approval owner.
2. Confirm applicable programmes · 3:30
Open Review applicability & route for ISO/IEC 27001. Set Applicable and include it. Rationale: the prospective customer requested an ISO/IEC 27001 readiness plan for the portal. Check the official ISO source at https://www.iso.org/standard/27001 for the exact edition and applicable amendments. Enter your actual source check date.
Record an internal readiness review followed by a certification body engagement if management proceeds. Leave the complete catalogue reconciliation unchecked for this sample. Leave other programmes unselected until their applicability is confirmed.
Say: We chose a programme for a specific business reason and are demonstrating a sample of its requirements.
3. Build the requirement register · 6:00
Choose Add a normative requirement. Use the official ISO link and verify references against your authorised copy. Record 6.1.3, Information security risk treatment, owner GRC Lead. Ask whether privileged-access risk links to a treatment decision, safeguards and approval.
Record 9.1, Monitoring, measurement, analysis and evaluation, owner Security Operations Lead. Ask who monitors privileged authentication, what they measure and how they escalate exceptions.
Record Annex A 8.5, Secure authentication, owner Identity Lead. Ask whether the chosen control covers ordinary human production administrators. Rationale: compromised credentials could expose customer data or permit production changes. HarbourPay chose MFA as its implementation and test criterion. Leave assessments unassessed until testing.
Say: Requirements describe what we assess. Controls describe how the organisation addresses them.
4. Design controls & working documents · 8:30
Add CTRL-IAM-01 — MFA for human production administrators. Owner: Identity Lead. Scope: ordinary human production administrators in Azure or the portal. Track emergency and workload identities separately. Entra Conditional Access targets the production admin group. Identity Operations reviews membership monthly and after role changes. Operating coverage is untested.
Acceptance: all ordinary human admins are subject to enforced MFA. Document approved emergency access exceptions, separate safeguards and monitoring. Check direct role assignments, policy state, exclusions and group membership. Set 30 November 2026 or a comparable next review date.
Create a working document titled HarbourPay SoA — secure authentication working extract. Map Annex A 8.5. Record selection rationale, the configured policy and pending operating verification. This is a sample Statement of Applicability entry.
Say: A policy can require MFA and still miss accounts. Specify the population, mechanism and evidence before testing.
5. Collect evidence & test controls · 11:30
Add EVD-001 — Production admin population. Point-in-time export of 12 ordinary human admins. Emergency and workload identities are tracked separately. Add EVD-002 — Conditional Access policy export. Enabled policy targets the admin group, but two direct assignments are outside it. The export shows configuration. Add EVD-003 — Simulated sign-ins. Two covered identities were prompted for MFA. Two uncovered identities reached the simulated admin service with a password alone.
Use Identity Operations as custodian and references such as DEMO-EVIDENCE/IAM/EVD-002. Label records fictional and use the closest available internal classification. Link all three references and CTRL-IAM-01 to the Annex A 8.5 assessment.
Test: reconcile all 12 role assignments against the enabled policy and exclusions. In a sandbox, test two covered and two uncovered identities. Expected result: MFA for every ordinary human admin. Actual: 10 of 12 records covered, two directly assigned identities missed and four simulated sign-ins reproduced the difference. Select the available result representing a gap and set High priority.
Consequence: stolen credentials could allow production changes or access to customer information. Reviewer: Security Assurance Reviewer. Use actual dates for verification and review activities you perform and label simulated evidence.
Say: The policy export shows configuration, the population review shows whom it misses, and sign-in testing shows why the gap matters.
6. Treat gaps & schedule reviews · 16:00
Create ACT-001 — Close MFA coverage gaps for two human production administrators. Link Annex A 8.5. Owner: Identity Lead. Priority: High. State: In progress. Internal due date: 20 November 2026 or a comparable future date. Escalate to COO if late or more gaps appear.
Confirm business need for each assignment, remove unnecessary privilege and bring retained privilege under enforced MFA. Test in the sandbox, obtain change approval and check for similar direct assignments.
Closure requires a fresh population export, coverage of all retained ordinary human admins, and retests showing both original exceptions are removed or challenged with MFA. Independent reviewer records the evidence. Leave completion and verification fields blank while open. Download the action calendar if useful.
Say: We have an accountable owner, a deadline, and a specific way to prove the fix.
7. Review readiness & handoff · 19:00
Show readiness metrics and catalogue checks. Record internal handoff review with the Security Assurance Reviewer and select Handoff with open findings. Notes: sampled scope only, full catalogue reconciliation outstanding, MFA gap open. Ask the COO to confirm owner and deadline, authorize retesting and decide when formal assessment readiness should be reviewed. Read and acknowledge the internal review statement after checking the register.
Say: Management can act today. A handoff records decisions and open findings. Formal assessment readiness is a separate decision.
8. Export, learn & maintain · 21:30
Choose Saved programme, including open findings, then Preview pack sections. Download Word for a management handoff, Excel to follow mappings, or PDF for a dated snapshot. Download and import the review calendar to create reminders.
On camera, trace ACT-001 back to Annex A 8.5, CTRL-IAM-01 and EVD-001 through EVD-003. After remediation, collect fresh evidence, independently retest and update the assessment and handoff.
Say: We started with a customer request and ended with a decision, an owner, a deadline and clear closure evidence.
Continue with the communityCompare your practice approach with other CyberJA Connect members.
Join CyberJA Connect ↗