Skip to content
Landfall
NIST CSF · NIST-CSF-GV-OC

NIST CSF GV.OC - Organizational Context

Establish and maintain understanding of organizational context — mission, stakeholder expectations, dependencies, and legal/regulatory requirements — to inform cybersecurity risk management decisions

HIGHRecommendationGovernanceTechnical standardIn forceApplies from 26 February 2024

Where this comes from

Provision: GV.OC - Organizational Context

Instrument: NIST Cybersecurity Framework 2.0 (February 2024)

Citation: NIST CSWP 29, The NIST Cybersecurity Framework (CSF) 2.0, 26 February 2024, Appendix A (CSF Core), GV.OC (Organizational Context), subcategories GV.OC-01, GV.OC-02, GV.OC-03, GV.OC-04, GV.OC-05

Text version: NIST CSWP 29, The NIST Cybersecurity Framework (CSF) 2.0, 26 February 2024, Appendix A (CSF Core); retrieved from nvlpubs.nist.gov on 2026-09-23.

Read the official text ↗

Who it applies to

It applies when all of these are true:

  • Data categories collected — any answer

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

  • Implementation or documented process meets the reviewed acceptance criteria; identify the tested version and deployment status separately
  • Configure defaults from the assessed source and purpose; do not enable data collection or processing merely because this task exists
  • Validate behavior for the assessed actors and use cases, including applicable guest or administrator paths
  • UI clearly communicates what the feature does to users
  • API returns appropriate error codes when feature blocks an action

Questions people ask

Does NIST CSF GV.OC - Organizational Context apply to my service?
It applies when Data categories collected — any answer.
From when does this apply?
NIST CSF GV.OC - Organizational Context applies from 26 February 2024. Its current status is: in force.

Find out whether this one lands on you

Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.

Run the pre-scanAll NIST CSF obligations

Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.

What Landfall Is NOT

Critical Boundaries

Understanding these boundaries is essential before using this product. Misuse of this tool for purposes outside its scope may create legal, regulatory, or commercial risk for your organization.

NOT Legal Advice

This product does not provide legal advice and does not create an attorney-client relationship.

Interpretations are informational analysis, not legal counsel. Always consult qualified legal professionals for compliance decisions.

NOT a Risk Score

We do not quantify, calculate, or certify your compliance risk level.

No numerical risk rating, compliance percentage, or safety score. Risk assessment requires human judgment about your specific context.

NOT Runtime Enforcement

This is a planning and mapping tool, not a runtime enforcement system.

Does not integrate with your production systems. Does not block, filter, or enforce compliance in real-time. Implementation is your responsibility.

NOT Regulatory Approval

Using this tool does not mean you are compliant with any regulation.

No certification, seal of approval, or compliance guarantee. Regulators will evaluate your actual implementation, not your use of this tool.

NOT Authoritative Interpretation

Our interpretations are not binding and may differ from regulatory guidance.

Only regulators and courts provide authoritative interpretation. Our analysis reflects our reading of requirements, which may be incomplete or incorrect.

NOT a Safe Harbor

This tool does not shield you from enforcement actions or liability.

Documentation of your process is valuable, but does not constitute a legal defense. Compliance is ultimately your organization's responsibility.

NOT an AI Compliance Agent

AI features assist analysis but do not make compliance decisions for you.

AI-generated interpretations require human review and approval. Automated suggestions are starting points, not final answers.

NOT Complete Coverage

We do not cover all regulations, all obligations, or all jurisdictions.

Regulatory landscape is vast and evolving. Gaps in our coverage do not mean those requirements don't apply to you.

What This Tool IS:

  • A structured workflow for mapping regulatory requirements to implementation tasks
  • A documentation system for compliance decisions (audit trail)
  • A collaboration platform for compliance, legal, and engineering teams
  • An informational resource for understanding regulatory obligations