OWASP ASVS
Give developers, testers and buyers a shared checklist for application security.
NIST Cybersecurity Framework 2.0
Create a common view of cybersecurity risk and turn gaps into an action plan.
Organizations of any size seeking an outcomes-based way to govern and improve cybersecurity risk.
Current and Target Organizational Profiles and a prioritized improvement plan.
CSF outcomes provide a common language. Choose implementation controls based on your risks, obligations and resources.
Track high-priority target outcomes without evidence, open work whose dependencies have slipped and risks that have passed their approval expiry.
Fill this in with your sponsor and send it to the people who own the work.
NIST CSF 2.0 kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Set the profile scope · Risk lead + leadership [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Choose an essential service and map who relies on it, what can interrupt it, and which suppliers and teams keep it running. 2. Inspect one real outcome from each function relevant to your scope. For example, restore one workload and time how long it takes. 3. Review the gaps with the sponsor. Choose the first funded change, its owner, and how the business will confirm it worked.
Checklist, instructions and 11 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Set the profile scope | Risk lead + leadership | At initiation | Set a start date | Scope memo; Stakeholder list; Risk context | Open |
| Build the Current Profile | Security + service owners | After discovery | Set a start date | Current Profile; Evidence inventory | Open |
| Set the Target Profile | Leadership + risk owners | After current state assessment | Set a start date | Target Profile; Gap analysis; Funding decision | Open |
| Execute and refresh | Control owners | Ongoing | Set a start date | Action plan; Measures; Updated profiles | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Set business objectives, critical services, obligations and stakeholders. Decide which environments and third parties belong in the profile.
Business objectives, inventory, stakeholder requirements, recent incidents and critical service maps.
The scope says that fulfillment depends on the warehouse API and identity provider and names the owners who verified those dependencies.
Escalate an essential service whose owner or upstream dependencies are unknown.
Fictional details. Use the same fields with evidence from your work.
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.
Fictional details. Use the same fields with evidence from your work.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Fictional details. Use the same fields with evidence from your work.
The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.
Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.
Map existing cybersecurity outcomes across Govern, Identify, Protect, Detect, Respond and Recover. Link each assessed outcome to evidence.
Selected outcomes, actual configurations, tickets, security events and recent test results.
One current outcome links to the last restore test and states that the order processing database recovered successfully while the queue dependency was outside the test.
Raise an outcome recorded as achieved when a critical dependency has never been tested or observed.
Fictional details. Use the same fields with evidence from your work.
The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.
Use approved gaps to prioritize the roadmap and refresh the baseline after the next review.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Prioritize target outcomes with stakeholders. Use Tiers where useful to communicate the rigor of risk governance and management.
Current Profile, impact tolerances, known threats, cost estimates and work dependencies.
The target says the order service, including its queue, must restore to the agreed business tolerance and identifies the exercise that will demonstrate it.
Raise any target that lacks a funding decision, an owner or a test.
Fictional details. Use the same fields with evidence from your work.
The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.
Use approved gaps to prioritize the roadmap and refresh the baseline after the next review.
Fictional details. Use the same fields with evidence from your work.
The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.
Use approved gaps to prioritize the roadmap and refresh the baseline after the next review.
Fictional details. Use the same fields with evidence from your work.
The minutes identify the person who approved each action and the date the decision will be revisited.
Give owners the actions and add the approved record to the relevant audit or governance file.
Assign remediation actions, measures and review dates. Refresh profiles after major changes or significant incidents.
Funded action plan, baseline evidence, implementation records and risk approval decisions.
A before-and-after test connects the funded work to the updated profile and records what still needs attention.
Escalate missed commitments affecting essential services or relevant risks accepted beyond their approval date.
Fictional details. Use the same fields with evidence from your work.
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.
Fictional details. Use the same fields with evidence from your work.
The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.
Use approved gaps to prioritize the roadmap and refresh the baseline after the next review.
Fictional details. Use the same fields with evidence from your work.
The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.
Use approved gaps to prioritize the roadmap and refresh the baseline after the next review.