Build a 90-day GRC programme for HarbourPay, a fictional cloud payment operations company. Progress through the decisions of a Compliance Analyst, GRC Analyst, GRC Lead and GRC Manager.
Allow 25–35 hours across several sessions. Start with basic security concepts and spreadsheet skills. You can complete the work in your own documents or use CyberJA’s existing workspaces.
STAGE 01 · Foundations · 2 hours
Start with the role and business objective
The situation
HarbourPay needs a usable GRC programme in 90 days to support enterprise customer onboarding. You are joining a four-person assurance team. Start as a Compliance Analyst, then work through the decisions an Analyst, Lead and Manager would own.
Terms you need
GRC means governance, risk management and compliance. Governance establishes who decides and checks results. Risk management deals with uncertain events and their consequences. Compliance identifies and assesses obligations. A RACI assigns who is responsible, accountable, consulted and informed.
This is how you would approach the task
- Write a one-page engagement brief naming the customer objective, in-scope portal, Azure, Entra ID, GitHub, service desk and payroll supplier. Record where supplier dependencies remain in scope.
- Choose your initial target role. Build a responsibility-to-evidence map covering compliance review, risk assessment, control testing, reporting and escalation.
- Assign COO as sponsor, Engineering as system and control owner, GRC as coordinator, and Security Assurance as independent reviewer. Name who can accept risk.
What you will produce
Use role-map.csv and engagement.csv. Deliver a scope statement, role map and RACI.
Compare with the worked reasoning
The Compliance Analyst reconciles requirements and evidence. The GRC Analyst connects registers and operating processes. The Lead sets priorities and governance. The Manager owns resources, escalation and programme performance. A control owner implements a fix; a GRC analyst tracks and tests the evidence.
Check your result
Each responsibility has an action, deliverable, owner and decision recipient. Boundaries include supplier interfaces.
Use the related CyberJA tool ↗
STAGE 02 · Compliance Analyst · 90 minutes
Plan the compliance assessment
The situation
The COO says the prospective customer wants a security readiness pack. A sales colleague interprets this as a requirement to obtain every available certification. You must clarify the actual engagement.
Terms you need
An obligation is a requirement from a source such as a contract, law, standard or internal policy. Applicability explains why it applies. A gap is the difference between an agreed criterion and the evidence observed.
This is how you would approach the task
- Read the fictional customer request: provide a security readiness plan, an access control overview and remediation dates within 90 days.
- Record ISO/IEC 27001 as the selected readiness reference for this exercise. Verify exact requirements from an authorized source before using them in a real assessment.
- Create a three-week assessment plan covering interviews, source review, evidence requests, testing and sponsor review. Record unresolved jurisdiction and payment-flow questions.
What you will produce
Use obligations.csv and engagement.csv. Deliver an assessment scope and evidence request list.
Compare with the worked reasoning
The request supports an ISO readiness exercise; the fictional facts do not establish obligations under GDPR, PCI DSS or other programmes. Mark those as needing applicability confirmation. Ask about actual data flows and contract terms before deciding.
Check your result
Every obligation has a source, rationale and owner. The plan gives dates and evidence requests.
Use the related CyberJA tool ↗
STAGE 03 · Compliance Analyst · 2 hours
Assess gaps and map controls
The situation
You receive an access policy, a role export, a Conditional Access summary and a change tracker. A written policy alone does not establish that administrators are covered.
Terms you need
A control is an action or mechanism that changes risk. Control design asks whether it could meet the objective. Operating effectiveness asks whether it worked during the assessed period. Mapping links controls to the requirements they support.
This is how you would approach the task
- Create three assessment objectives: controlled privileged access, timely removal after role changes and authorized production releases. Use internal policy as the exact exercise criterion.
- Map MFA enforcement, monthly access reconciliation and release approval to the corresponding objective. One control can support several objectives.
- Compare each criterion against the synthetic evidence pack. Record findings with evidence IDs, actual results and business consequences.
What you will produce
Use control-library.csv and compliance-matrix.csv. Deliver a traceable gap assessment.
Compare with the worked reasoning
Policy requires MFA for ordinary human production admins. EVD-01 lists 12 accounts. EVD-02 targets a group containing 10 of them. EVD-03 shows two uncovered accounts reaching the sandbox service without MFA. The MFA criterion is partly implemented. Record a high-priority gap. Emergency and workload identities are assessed separately.
Check your result
Findings cite records and show criterion, condition and consequence. Design and operation are assessed separately.
Use the related CyberJA tool ↗
STAGE 04 · Compliance Analyst · 2 hours
Collect evidence and support audit
The situation
An auditor asks for proof of the last quarter’s access reviews. An administrator sends an undated screenshot. Decide what further evidence is needed.
Terms you need
Evidence provenance records where a record came from and who collected it. Population is the full set of items relevant to a test. A sample is a selected subset. A point-in-time export cannot establish three months of operation.
This is how you would approach the task
- Build an evidence index with observation date, owner, scope, period, repository reference, limitations and refresh date.
- Request reviewer decisions, the dated entitlement population and proof that rejected grants were removed. Record the original screenshot as incomplete for this objective.
- Write a short response to the auditor with evidence IDs, what they demonstrate and any uncovered period. Maintain a request log and record follow-up.
What you will produce
Use evidence-index.csv and audit-requests.csv. Deliver a draft audit response.
Compare with the worked reasoning
An undated settings screenshot may illustrate a configuration but cannot prove quarterly review operation. Ask for the dated review decision file, population and removal record. For external assessment, the assessor makes the formal assessment decision. GRC coordinates evidence and resolves open questions.
Check your result
A reviewer can reproduce the finding using the referenced evidence. Missing periods and sample limitations are explicit.
Use the related CyberJA tool ↗
STAGE 05 · Compliance Analyst · 2 hours
Log risks and handle exceptions
The situation
Engineering needs two weeks to change admin authentication. Payroll wants to keep an old remote-access method for six weeks. Both request an exception.
Terms you need
Inherent risk is assessed before considering the controls in the scenario. Residual risk remains after evaluating controls. A risk exception is a documented, time-limited decision to depart from a requirement with identified safeguards and accountable approval.
This is how you would approach the task
- Use the exercise scoring scale in the starter pack. Write R-01 for uncovered administrator access, R-02 for payroll supplier access and R-03 for recovery data loss.
- For each, describe the threat event, exposed service, consequence, owner, current controls and remaining uncertainty. Rate likelihood and impact with reasons.
- Prepare EX-01 for payroll remote access with scope, temporary safeguards, expiry, approver, monitoring and a permanent fix. Route high residual exposure to the COO.
What you will produce
Use risk-register.csv and exceptions.csv. Deliver a prioritized risk register and one exception decision.
Compare with the worked reasoning
R-01 likelihood 4 × impact 5 = 20, Critical on this fictional scale. If enforcement is verified for every retained account, likelihood might fall to 2 while impact remains 5, giving 10, High. This is a reasoned estimate, not a measured loss forecast. Proposed safeguards do not reduce the recorded current risk until verified.
Check your result
Risk acceptance has a named authority and expiry. The analyst recommends and escalates; the authorized owner records the decision.
Use the related CyberJA tool ↗
STAGE 06 · GRC Analyst · 2 hours
Build the GRC blueprint and operating model
The situation
The team has separate spreadsheets for risk, policy, testing and audit. Nobody can tell which open actions relate to the biggest customer onboarding risks.
Terms you need
A blueprint describes the connected components of a programme. An operating model defines people, processes, decisions, information and recurring routines. Traceability lets a reader move between related records.
This is how you would approach the task
- Draw the path business objective → obligation → risk → control → evidence → finding → action → management decision.
- Assign stable IDs such as R-01, C-01, EVD-01 and A-01 across all files. Define the owner, update trigger and review cadence for each register.
- Set a weekly remediation meeting, monthly risk review and quarterly executive review. Document what decisions each forum can make and when it escalates.
What you will produce
Use operating-model.csv and the shared record IDs. Deliver a two-page GRC blueprint.
Compare with the worked reasoning
Customer onboarding depends on privileged access assurance. R-01 maps to C-01, EVD-01/02/03, finding F-01 and action A-01. Identity owns implementation, GRC maintains the mapping, Security Assurance retests, and COO decides resources and exceptions.
Check your result
The model shows inputs, outputs, accountabilities and decision rights. Updates flow through linked records.
Use the related CyberJA tool ↗
STAGE 07 · GRC Analyst · 2 hours
Develop policy, standard and procedure
The situation
HarbourPay has a policy requiring secure access but does not define the administrator population or explain how missed accounts are identified.
Terms you need
A policy states management intent. A standard sets specific requirements. A procedure describes execution. Policy governance controls authorship, approval, version, review and exceptions.
This is how you would approach the task
- Draft a short access policy with purpose, scope, owner, responsibilities and exception route.
- Write a standard requiring enforced MFA for ordinary human production administrators and defining the review of role assignments and exclusions.
- Write a reconciliation procedure: export assignments, compare with enforcement scope, investigate exceptions, obtain decisions, implement changes and verify closure. Add approval and review fields to the policy register.
What you will produce
Use policy-register.csv. Deliver one policy, standard and procedure extract.
Compare with the worked reasoning
Policy: protect production access through approved and reviewed permissions. Standard: every retained ordinary human admin must have MFA enforcement, with any emergency access handled under documented separate safeguards. Procedure: reconcile all role assignments, rather than relying only on membership of the target group.
Check your result
The three documents serve distinct purposes and reference each other. A reader can identify who performs and approves each step.
Use the related CyberJA tool ↗
STAGE 08 · GRC Analyst · 90 minutes
Integrate GRC into business operations
The situation
New suppliers, emergency releases and job transfers happen outside the monthly GRC meeting. Controls must enter these workflows at the point decisions are made.
Terms you need
A trigger is an event that starts a process. A gate is a required check before a step proceeds. An evidence workflow defines when records are created, where they are kept and who reviews them.
This is how you would approach the task
- Design entry checks for procurement, employee transfers and production changes. Specify a trigger, required evidence, accountable approver and escalation.
- Run a fictional job transfer: HR notifies the owner, access is reviewed, rejected grants are removed and a fresh export verifies the change.
- Draft a management status note showing implemented workflow changes, remaining gaps and decisions needed.
What you will produce
Use operating-model.csv and stakeholder-plan.csv. Deliver three workflow sketches and one status note.
Compare with the worked reasoning
Procurement routes a payroll supplier for review before data transfer. HR transfer triggers entitlement reconciliation. Production releases require approved change evidence or an emergency route with retrospective review. Each workflow generates evidence naturally.
Check your result
Checks appear before the relevant risk is introduced, and the evidence producer and reviewer are identified.
Use the related CyberJA tool ↗
STAGE 09 · GRC Lead · 2 hours
Set strategy and the roadmap
The situation
The COO proposes buying a new dashboard while exploited exposure and access exceptions remain unresolved. The Lead must align work with the 90-day objective.
Terms you need
Strategy connects business goals to choices about priorities and resources. A roadmap orders outcomes over time. A dependency is work that must happen before another outcome is achievable.
This is how you would approach the task
- Write three outcomes: close critical access gaps, establish auditable control evidence and make escalation work before customer handoff.
- Create a 30/60/90-day roadmap with accountable owners, dependencies, resources and measurable acceptance criteria.
- Explain to the COO why identity remediation and evidence quality precede new reporting automation. Include the consequences of delaying either.
What you will produce
Use roadmap.csv. Deliver a one-page strategic roadmap.
Compare with the worked reasoning
Days 1–30: reconcile access and verify the two exceptions. Days 31–60: stabilize recurring reviews, supplier oversight and evidence production. Days 61–90: independently retest, review programme coverage and prepare the customer readiness handoff. Dashboard automation follows reliable source data.
Check your result
Each initiative supports a business outcome and has a success measure. The order reflects risk and dependencies.
Use the related CyberJA tool ↗
STAGE 10 · GRC Lead · 2 hours
Lead enterprise risk and governance
The situation
IT scores technical findings while Finance tracks supplier downtime. The executive team needs one view of business exposure with consistent decision routes.
Terms you need
Risk appetite expresses how much and what types of exposure an organization is prepared to accept in pursuit of its goals. A threshold triggers a defined response. Aggregation groups related exposure without adding incompatible ordinal scores.
This is how you would approach the task
- Apply the fictional appetite rules to all three risks and record an escalation route. Group R-01 under customer service integrity, R-02 under supplier dependency and R-03 under recovery.
- Design a risk committee charter with membership, quorum, authority, cadence and required decision records.
- Explain how related findings might share one underlying identity control failure. Avoid counting them as independent losses.
What you will produce
Use risk-register.csv and governance-charter.csv. Deliver an enterprise risk summary and committee charter.
Compare with the worked reasoning
For this exercise, Critical risk requires immediate COO escalation and cannot be accepted by a system owner. High exposure requires COO decision within five working days. A quarterly board review discusses material trends; it does not replace urgent escalation. These are scenario rules, not universal thresholds.
Check your result
Decision authority matches the appetite. Material issues can be escalated between scheduled meetings.
Use the related CyberJA tool ↗
STAGE 11 · GRC Lead · 90 minutes
Build controls and compliance oversight
The situation
Several teams report their controls as green based on policy existence. You need a consistent control library and an assessment method that tests operation.
Terms you need
A common control can support multiple obligations. A control owner operates the control. An assessor evaluates it. A coverage map shows which obligations have assessed supporting controls and which still lack evidence.
This is how you would approach the task
- Add C-01 MFA, C-02 access reconciliation, C-03 release authorization and C-04 restoration validation to the library.
- Give each control a scope, owner, frequency, population, expected evidence and acceptance criterion. Link internal exercise obligations without claiming full ISO catalogue coverage.
- Schedule independent tests and record failed, partial and unassessed results separately. Identify the resource needed to complete the missing tests.
What you will produce
Use control-library.csv, compliance-matrix.csv and evidence-index.csv. Deliver a common control framework and testing plan.
Compare with the worked reasoning
C-04 targets 120-minute service recovery and 15-minute maximum data loss. EVD-05 shows 90 minutes and 25 minutes respectively. One recovery target was met and the other was missed. A green status for the entire control would hide a business consequence.
Check your result
Unassessed controls remain visible. Mapping to a framework does not itself demonstrate implementation or effectiveness.
Use the related CyberJA tool ↗
STAGE 12 · GRC Lead · 90 minutes
Assess supplier risk
The situation
PayServe, a fictional payroll vendor, stores staff bank details and supports payday processing. Its report covers a different service and contains an unresolved access exception.
Terms you need
Inherent supplier exposure depends on the service, data, access and business dependency. Assurance scope determines what a supplier report actually covers. A concentration risk exists when a critical dependency has few viable alternatives.
This is how you would approach the task
- Tier PayServe using data sensitivity, system access, criticality and switching difficulty. Identify what happens if it is unavailable on payday.
- Record the mismatch between the reviewed report and the contracted service. Ask for matching coverage and follow-up on the access exception.
- Recommend onboarding conditions, accountability for gaps, a review date and triggers such as a service change or incident.
What you will produce
Use vendor-risk.csv. Deliver a supplier assessment and decision memo.
Compare with the worked reasoning
Classify the vendor as critical within the scenario because it handles banking data and an essential payroll dependency. Request evidence for the actual service and period. A high-level report title alone is insufficient. COO and Finance decide whether safeguards and continuity arrangements allow the service to proceed.
Check your result
The decision is specific to the contracted service. Evidence gaps, conditions and residual exposure are explicit.
Use the related CyberJA tool ↗
STAGE 13 · GRC Lead · 2 hours
Build an executive dashboard
The situation
Management receives long lists of closed tickets but cannot see whether critical exposure is decreasing. You must build measures that support decisions.
Terms you need
A KPI measures process performance. A KRI indicates exposure. Every measure needs a definition, period, source, owner and response threshold. A denominator explains the full population used in a percentage.
This is how you would approach the task
- Calculate production admin MFA coverage from EVD-01/02: 10 divided by 12, or 83.3%. Label it as population coverage, not organization-wide compliance.
- Calculate overdue high-priority actions at the fixed scenario snapshot. Show numerator and denominator and distinguish initial state from a later retest.
- Add recovery RPO performance, evidence freshness and expired exceptions. Write three decision-oriented observations for the board.
What you will produce
Use dashboard.csv. Deliver a dashboard and a three-slide executive brief.
Compare with the worked reasoning
At the starter snapshot, 2 of 4 high-priority actions are overdue, or 50%. One of two exception records is expired, also 50%. The payroll restore loses 25 minutes against a 15-minute target. Show each source and date. Do not average these measures into an unsupported compliance score.
Check your result
Another reviewer can reproduce each number. Each breached threshold has an owner and response.
Use the related CyberJA tool ↗
STAGE 14 · GRC Lead · 90 minutes
Influence stakeholders and build risk culture
The situation
Engineering says the access change will delay a release. Finance says a supplier restriction will affect payroll. You need a decision without dismissing either business constraint.
Terms you need
Stakeholder influence connects evidence with the other person’s objectives and constraints. Risk culture is reflected in how people raise issues, record decisions and respond to mistakes. An escalation preserves accountable decisions when agreement fails.
This is how you would approach the task
- Draft a five-minute meeting plan stating the shared objective, evidence and options. Offer a phased change with sandbox verification and a clear deadline.
- Write an email to Engineering explaining the two uncovered accounts, impact, proposed change window and decision requested.
- Define a safe way for teams to report access or evidence problems early. Measure timely reporting and closure, and record unresolved dissent in the decision log.
What you will produce
Use stakeholder-plan.csv and decisions.csv. Deliver a meeting record and two communications.
Compare with the worked reasoning
Ask Engineering which release dependency creates the delay. Offer removal of unnecessary privilege immediately and a controlled change for retained access. If High exposure remains beyond authority, route the decision to the COO with the options and consequences. Record the business owner’s decision accurately.
Check your result
Communications include the evidence, business consequence, options, decision owner and next checkpoint.
Use the related CyberJA tool ↗
STAGE 15 · GRC Manager · 2 hours
Own the programme and resources
The situation
The team has 60 analyst hours available this month but requests total 100. A supplier review, remediation retest and dashboard redesign compete for capacity.
Terms you need
Programme ownership means accountability for outcomes, resources, dependencies, reporting and correction. A responsibility dashboard links role expectations to observable outputs and measures. Delegation assigns work while preserving the decision authority.
This is how you would approach the task
- Allocate 20 hours to access remediation verification, 20 to supplier evidence, 15 to recovery retest preparation and 5 to management reporting. Defer 40 hours of presentation redesign in this fictional plan.
- Create a manager responsibility map linking strategy, risk, compliance, controls, policy, suppliers, people and reporting to accountable owners and evidence.
- Define operating meetings, escalation times, review independence and a 90-day performance review. Record what happens if capacity or deadlines change.
What you will produce
Use manager-map.csv, roadmap.csv and decisions.csv. Deliver a resource plan and manager dashboard.
Compare with the worked reasoning
The resource decision protects critical dependencies and customer readiness evidence first. Dashboard cosmetics are delayed. The Manager records the deferred work, resource assumptions and impact. Control owners implement fixes; the Manager ensures capacity, escalation and verification are arranged.
Check your result
Every manager responsibility has a measure, an accountable owner and a review routine. Resources match priorities.
Use the related CyberJA tool ↗
STAGE 16 · GRC Manager · 90 minutes
Make the executive decision and handoff
The situation
The 90-day checkpoint arrives. One access action is verified, supplier evidence remains incomplete and the full normative catalogue has not been reconciled.
Terms you need
An internal readiness opinion states the scope, evidence and limitations of the work completed. A handoff transfers accountable actions and decisions. Formal certification or external assurance follows its own assessor process.
This is how you would approach the task
- Prepare a one-page brief with current exposure, progress, open gaps, resource decision and recommendation.
- Decide whether to proceed with customer handoff, restrict its claims or defer a formal external assessment. Name evidence needed to revisit the decision.
- Record management approval, owners, dates and the next review. Keep unresolved evidence and catalogue coverage visible.
What you will produce
Use decisions.csv and handoff.csv. Deliver a board brief and signed-off action ownership record.
Compare with the worked reasoning
Recommend a scoped readiness handoff with open findings, rather than claiming complete ISO readiness. State the completed scope, unresolved supplier coverage and missing catalogue reconciliation. Ask the sponsor to approve the remediation plan and reassessment date before scheduling any wider formal assessment.
Check your result
The recommendation follows evidence and discloses limitations. The decision log identifies who agreed and what remains open.
Use the related CyberJA tool ↗
STAGE 17 · Portfolio · 90 minutes
Build your portfolio and interview story
The situation
You have a connected set of work products. Turn them into a portfolio that explains your reasoning and shows the different levels of GRC responsibility.
Terms you need
A portfolio demonstrates work and judgement. Evidence provenance and limitations matter in an interview. A simulated project should be labelled clearly so a reader understands the experience it represents.
This is how you would approach the task
- Choose one artifact from each role: compliance gap assessment, GRC blueprint, Lead roadmap/dashboard and Manager decision brief.
- Write a CV bullet explaining the fictional scope, evidence examined and decisions supported. Label it Simulated GRC project.
- Prepare answers to: Why was R-01 Critical? What did the policy fail to cover? Why did you not mark the whole recovery control as passed? Which decisions required the COO? How would you improve the programme after 90 days?
What you will produce
Use portfolio.csv and the completion checklist. Deliver a sanitized portfolio with four role-based interview stories.
Compare with the worked reasoning
Example: Completed a simulated 90-day GRC engagement for a cloud service, reconciling 12 admin accounts, documenting two MFA coverage gaps, mapping controls to evidence and preparing a risk-based remediation roadmap and executive decision brief. Include assumptions and the limits of the sample.
Check your result
The portfolio traces at least one finding end to end and explains the difference between performed analysis and simulated outcomes.
Use the related CyberJA tool ↗