Job search
GRC Portfolio for Cybersecurity Jobs: Build a Current and Target Profile
A complete fictional Cedar Harbor profile and 40-hour gap decision show evidence boundaries, ownership, closure conditions and priorities without invented implementation.
A GRC portfolio can show how you turn incomplete evidence into a defensible cybersecurity decision. Build a scoped Current Profile, a distinct Target Profile and a prioritized action plan. Keep unknowns visible, name who would approve decisions, and explain what evidence would close each gap.
You do not need to invent an employer engagement to demonstrate that reasoning. This article uses an original fictional scheduling-service exercise, reviewed against current NIST resources on October 23, 2026. LandOffer publishes this guide; browse recent cybersecurity roles to compare requested governance, evidence-review and risk-communication work with the artifacts you can honestly show.

Scope the profile before filling the framework
The NIST Profiles page provides an Organizational Profile spreadsheet for comparing current and target outcomes. It also distinguishes Organizational Profiles from Community Profiles, which address shared interests across organizations. A self-authored portfolio exercise is not a newly established industry Community Profile.
Start with one service and a reason to examine it. The fictional Cedar Harbor example covers a customer scheduling service and its support process. Its stipulated business concern is appointment disruption if the service is interrupted. Two engineers and a shared support owner have an illustrative 40 staff-hours available this month. These are teaching assumptions, not interviews, observed controls or a real company's capacity.
The scope record identifies the review date, included service, assumptions and resource constraint. It excludes a complete enterprise assessment, real customer information and production changes. A reviewer can inspect the service boundary, the evidence gaps and the proposed decisions without assuming the exercise covers every system. It also prevents a statement about one service from silently becoming a claim about an entire organization.
NIST's Organizational Profiles quick-start guide treats scope, information gathering, profile creation, gap analysis and follow-through as connected work. For a portfolio, complete the analysis and planning artifacts you can support. Mark implementation and subsequent review as unperformed when they have not happened.
Separate the current evidence from the desired outcome
The current NIST FAQ distinguishes a Current Profile describing outcomes currently achieved and how, from a Target Profile describing desired outcomes. That distinction is the centre of this portfolio exercise. A policy that says multi-factor authentication is expected belongs in the evidence description; it does not establish that every relevant account enforces it.
Use plain status terms with definitions. In this fictional packet, “Partial” means the invented evidence describes some activity but leaves a named boundary unresolved. “Unknown” means the supplied packet cannot establish the outcome. “Not demonstrated” means the exercise contains no supporting result for the stated activity. None of these labels is a formal NIST rating scale or a finding about a real organization.
Unknown should not automatically become failed. If an analyst has not received administrator-enrollment evidence, they cannot conclude that MFA is absent everywhere. They can record what is missing, its importance, the owner who should resolve it and the consequence for the decision. Show that judgment directly in the Current Profile and the action you propose.
The CSF 2.0 publication organizes outcomes under GOVERN, IDENTIFY, PROTECT, DETECT, RESPOND and RECOVER. The selected themes below are editorial paraphrases aligned with those Functions, not exact subcategory quotations or a claim to assess the entire Core. No invented subcategory IDs are attached to make the table look authoritative.
Worked profile: Cedar Harbor's six selected themes
The complete local artifact is worked-assets/current-target-profile.md, with current-target-profile.csv and profile-scope.json in the same folder. These files contain the original completed editorial exercise, not collected employer evidence. All organization details, evidence descriptions, owners and targets are fictional. The finished profile records present uncertainty separately from a target and its closure condition; no row reports independent assessment or achieved remediation.
| Function and selected theme | Current evidence in the fictional packet | Target and evidence needed to close it |
|---|---|---|
| GOVERN: risk ownership | Draft note names Engineering but no individual approver or accepted outage threshold | Jo approves service scope, outage tolerance and escalation by day 7; retain a dated decision record. |
| IDENTIFY: dependencies | Service list contains the app and database but omits the notification provider | Sam reviews app, data store and notification dependency with owners by day 10; retain inventory and explicit omissions. |
| PROTECT: administrator access | Policy expects MFA; enrollment and exception evidence are not supplied | Mina reviews the administrator evidence and enforcement or exception decision by day 14; retain sanitized test and exception records. |
| DETECT: failure visibility | No notification-alert example, route or test result appears in the packet | Sam exercises a simulated failure and assigned response path by day 21; retain trigger, receipt and triage evidence. |
| RESPOND: communication | Contact list exists but severity, authority and communication decisions remain unresolved | Jo completes a communication tabletop by day 24; retain decisions and unresolved questions. |
| RECOVER: restoration | Backup schedule is stated but no restore output exists | Mina runs an authorized isolated restore exercise by day 28; compare a validated result with selected recovery objectives. |
The backup row makes the evidence distinction concrete. A schedule describes intended activity. A restoration record would need to show what was restored, under which conditions, how it was checked and how the result compared with the chosen objective. Merely rewriting the schedule as a target achievement would hide the central uncertainty.
The detection row has a separate limit. A simulated trigger, received alert and named triage owner could close the planned exercise task. It would not prove production alerts always arrive or that a real incident would be handled successfully. Put that limitation beside the closure condition rather than leaving a reviewer to infer it. A notification failure is an operational signal in this exercise. It does not by itself demonstrate discovery or analysis of a cybersecurity attack. A fuller security scenario would need to explain the adverse event, its relationship to a possible compromise and the evidence used to evaluate it. Keep that missing context explicit rather than presenting this selected theme as complete DETECT coverage.
The completed profile has six selected themes and six open targets. That count is a teaching boundary, not “six controls assessed” or a percentage of CSF coverage. It leaves room for additional outcomes that a genuine service assessment would identify after understanding its actual context and requirements.

Worked gap decision: allocate 40 hours without declaring success
The second original asset is worked-assets/gap-decision.md, accompanied by gap-action-plan.csv. Decision CH-01 is complete as a fictional planning memo. Jo, an invented product owner, selects six actions and records why a polished monitoring dashboard alone would be the wrong allocation for this exercise.
| Action | Fictional owner | Planning hours | Due date in the exercise | Reason and current disposition |
|---|---|---|---|---|
| A1: approve scope and risk owner | Jo | 4 | Day 7 | Establish authority for trade-offs and escalation; dated approval missing, OPEN. |
| A2: review administrator evidence | Mina | 8 | Day 14 | Resolve important access uncertainty; MFA evidence absent, OPEN. |
| A3: complete dependency inventory | Sam | 6 | Day 10 | Define restore scope and alert responsibility; owner review absent, OPEN. |
| A4: isolated restore exercise | Mina | 12 | Day 28 | Examine ability to resume the scoped service; no result, OPEN. |
| A5: notification-alert exercise | Sam | 6 | Day 21 | Connect a simulated detection to an owner; no output, OPEN. |
| A6: communication tabletop | Jo | 4 | Day 24 | Use A1's decisions and align communication with A5; no tabletop output, OPEN. |
| Total | Three fictional owners | 40 | This illustrative month | All estimates are planning inputs, not measured effort or completed work. |
The arithmetic is 4 + 8 + 6 + 12 + 6 + 4 = 40. A4 receives 12 hours because the scenario's restoration evidence is absent and service continuity matters to its stipulated purpose. This is an explained judgment under invented constraints, not an industry benchmark for restore testing or a universal ranking of security work.
Keep effort and elapsed time separate. Forty staff-hours is the exercise's resource allowance, while day 7 through day 28 are proposed deadlines relative to an unspecified start. The example does not demonstrate that the fictional owners are available, that approvals arrive on time or that the estimate is sufficient. A reviewer can challenge those assumptions without changing the arithmetic.
The plan also needs a rule for new evidence. If an inventory review identifies another critical dependency, record the finding and reconsider the affected restoration and alert tasks. Do not keep the original allocation simply because the table already totals 40. Explain what you would defer, who could approve the change and which target stays open. That decision trail shows how the plan responds to uncertainty instead of treating a completed spreadsheet as the end of the work.
Action IDs are not a strict execution sequence: the dependency inventory is due before the administrator-evidence review. A1 establishes decision authority; A3 informs restoration scope; A5 and A6 connect detection with communication. Those dependencies let a reviewer test whether the proposed work can happen in the stated order and whether each owner has the information needed.
CH-01 rejects spending all 40 hours on a dashboard because that would leave ownership, access evidence and restoration unresolved. Its escalation rule is also finished: if access evidence is unavailable by day 14, keep the status unknown and request a decision from the named fictional owner. If restore output is missing on day 28, keep the target open and revise the plan. Neither absence becomes an invented successful control.
Keep the profile distinct from certification and compliance
NIST's FAQ says it does not certify or endorse CSF products, implementations or services. Do not label this portfolio “NIST certified,” use a fabricated approval badge, or imply a reviewer has issued an audit opinion. Present the traceable analysis and decision record under your own authorship, with the fictional scope visible.
The same FAQ explains that the CSF provides outcomes to prioritize and address risk rather than a recommended checklist of actions for every organization. A six-row sample cannot establish compliance with an unnamed law or customer contract. A real compliance question would require the applicable obligations, scope and evidence, not a universal claim derived from framework headings.
Tiers are a further distinction. They characterize cybersecurity risk governance and management practices; this exercise assigns none. It does not turn six open targets into a maturity score, claim a Tier improvement or calculate risk reduction from planned hours. A percentage or Tier improvement would require a defined assessment and supporting evidence; the 40-hour planning total supplies neither.
A genuine decision to accept risk would also need its own authority, scope, rationale and review date. CH-01 describes escalation but does not invent an approved acceptance. Leaving that boundary explicit demonstrates that identifying a gap, selecting work and accepting residual risk are different decisions.
Present the portfolio as work you actually performed
A concise case-study opening can state: “Created a self-authored fictional CSF 2.0 profile exercise for one scheduling service; documented evidence gaps, target closure conditions and a 40-hour action plan.” That describes the work in this packet without claiming you implemented MFA, restored a production database or led an employer audit.
Keep the scope, profile and decision together. The local CSV and Markdown files let a reviewer trace a target to its action, owner and closure evidence. They are local artifacts, not a deployed public portfolio. Before sharing a hosted copy in an application, check actual access and remove identifiers, customer records, real topology and confidential evidence.
If you later perform an authorized lab exercise, add its dated result as new evidence and explain which target it supports. Preserve the original assumptions so the change can be understood. Do not quietly rewrite an unperformed plan into a past-tense accomplishment simply to strengthen a résumé bullet.
Choose one small service and complete its scope, Current/Target comparison and gap decision before adding more outcomes. Then compare recent roles on LandOffer.ai and identify three requested GRC responsibilities your actual portfolio work demonstrates.
Download the worked example files
Download the companion example files. The archive contains the original educational artifacts discussed above. Review its README and source before running code; fictional inputs and local test results retain the limits stated in this article.


