EVOPEDIA

← all systems · see it in The System

Security policy and governance

A definition of what it means to be secure for a system, organisation or other entity, constraining the behaviour of its members and, through mechanisms, its adversaries (src:wp:security-policy); in an organisation, the aggregate of directives, regulations, rules and practices that prescribes how it manages, protects and distributes information (src:nist-sp800-12r1), set and owned through information security governance: the framework, management structure and processes that align security strategy with business objectives, keep it consistent with laws and regulations through policies and internal controls, and assign responsibility (src:nist-sp800-100). Walked as governance practitioners and researchers describe it: requirements taken in (law, mission, risk, standards, suppliers), turned into a hierarchy of policies, standards and procedures, owned through roles and accountability, overseen by monitoring, evaluation and audit, and directed by the governing body; with the formal (machine) sense of 'security policy' (Bell-LaPadula, Biba, Clark-Wilson) kept on the shelf as kinds.

Properties published scienceour proposal

Sourced fields, and our own readings.

born atcontested (see C-1732)
born precisioncontested
boundaryInside: the policy set (program, issue-specific and system-specific policy, with the standards, guidelines and procedures under them), the governance structure that owns it (governing body, executives, the CISO or senior information security officer, policy development team, roles, responsibilities and authorities), and the oversight processes (direct, monitor, evaluate, communicate, assure; management review and internal audit). Outside: the members whose conduct it constrains (each a person with their own channels), the mechanisms that enforce it once configured (access control, monitoring), the risks it answers (risk management), the laws, regulators and standards bodies that shape it, external auditors and certification bodies, and suppliers bound by contract.
nested levelA practice inside organisations: part of the organisation's decision and control (corporate governance, of which IT governance is a subset), and the governing floor of computer security (CSF GOVERN at the centre of the wheel). Law and standards shape it from outside; members and mechanisms carry it out.
scalesocial

Measures (22) published science

characteristic clock: policy review cycleat least 1 per year
ISO/IEC 27001 surveillance audit intervalfirst within 12 months, then at least once each calendar year
ISO/IEC 27001 recertification cycle3 years
FISMA program review1 per year
US agency strategic plan refresh (GPRA)within 3 years
NIST CSF 2.0 Core size6 Functions, 22 Categories, 106 Subcategories count
NIST CSF 2.0 GOVERN size6 Categories, 31 Subcategories count
ISO/IEC 27001:2022 Annex A controls93 in 4 themes (2013 edition: 114 in 14 clauses) count
ISO/IEC 27001 certificates (2022 survey)>70,000 in 150 countries certificates
CISO reporting lines (2019)24% to CIO, 40% to CEO, 27% to the board % of CISOs
businesses with a CISO or equivalent (GSISS 2018)85 %
US federal security share of IT spending (FY 2008)$6.2 billion of about $68 billion (about 9.2%) USD
NIS2 maximum administrative finesEUR 10 million or 2% of worldwide turnover (essential); EUR 7 million or 1.4% (important) EUR / %
psychological contract breach -> ISP compliance intentionpath coefficient -0.195, p = 0.002, n = 206 UK employees PLS path
contingent staff: attitude -> compliance intentionbeta = 0.586, f2 = 0.376, n = 688 PLS path
contingent staff: knowledge sharing -> attitudebeta = 0.411 (certainty of detection 0.287; severity of punishment 0.313; subjective norm 0.352; collaboration 0.269) PLS path
breaches involving contract or temporary workers (US, as cited)nearly 50 %
security decision game208 sessions, 948 players; 30% of teams went bust; no background significantly better count
health ISB studies on policy and regulation compliance17 (of 25 on desired security behaviour) studies
policy management practices7 practices in 3 stages, from 112 papers (1994-2015) count
policy-as-code study size399 repositories, 9 tools; DevOps infrastructure 17% of projects count
first CISO title1995 year

Open contentions (5) open contention

Where sources or readings disagree. Both stay on the map.

Partners and parts published science

Built from / builds (9)

Sits inside / holds (6)

Trades with (valence) (16)

expressed by (17)

floor filled by (16)

Kinds (4)

Notes published science

Layers

The ways it takes in its world, where they meet, and how it acts back, each from L1 (where it meets the world) up.

security policy and governance as governance practitioners and researchers describe it: the organisation's people, information and systems and the requirements on them, up to the direction its governing body sets (reader's view)

  1. L1: The organisation's people, information, systems and facilities, and the adversaries around them: what the policy constrains (members' behaviour; adversaries through doors, locks, keys and walls; functions, flows and access in systems)
  2. L2: Organisational context taken in: mission, stakeholder expectations, dependencies, and legal, regulatory and contractual requirements understood (GV.OC); security needs determined
  3. L3: Security requirements identified: what the organisation must achieve, from risk assessment results, existing policies and outside requirements; security objectives commensurate with risk
  4. L4: The policy set: program, issue-specific and system-specific policy, with organisational standards, guidelines and procedures under them; drafted, reviewed and approved
  5. L5: Roles, responsibilities and authorities: leadership accountable, CISO/SAISO, offices, resources allocated; a centralised, decentralised or hybrid structure
  6. L6: Oversight: monitor and evaluate (management review, internal audit, metrics), strategy reviewed and adjusted; risk appetite and tolerance held
  7. L7: Direction by the governing body: security strategy aligned with business objectives, laws and regulations, responsibility assigned, all to manage risk

the boardroom (shared floors)

  1. L4: The policy set: program policy (purpose, scope, responsibilities, compliance), issue-specific and system-specific policy, and the standards, guidelines and procedures that implement them; drafted by a policy team of stakeholders, reviewed and approved by top management
  2. L5: Roles, responsibilities and authorities: leadership accountable; the CISO or SAISO directing the program; offices and resources assigned; structure centralised, decentralised or (usually) hybrid
  3. L6: Oversight: monitor (check compliance) and evaluate (compare with objectives, decide changes); management review, internal audit, metrics; the CISO interprets for senior management
  4. L7: The governing body (board and executives) directs: sets priorities, objectives and risk appetite, communicates expectations about accountability and resources, holds fiduciary responsibility

way in: Audit and assurance (internal audit, inspector general, certification bodies)

  1. L1: System records, activities and related documents examined independently
  2. L2: Internal audits and management reviews at planned intervals; external surveillance audits
  3. L3: Nonconformities found and corrective action required

way in: Laws, regulations and contracts (FISMA, NIS2, GDPR, PCI DSS, contracts)

  1. L1: Laws, regulations and directives that establish responsibilities, minimum controls and compliance reporting
  2. L2: Legal, regulatory and contractual requirements understood and managed (GV.OC-03); legal counsel consulted on penalties
  3. L3: Balanced against agency-specific policy, which may be more stringent than the law

way in: Members' conduct and feedback (compliance, workarounds, attitudes)

  1. L1: What members actually do under the policy: comply, violate unintentionally, or work around it (shadow security)
  2. L2: Feedback collected from managers and users by interviews and surveys; compliance monitored
  3. L3: Feedback analysed for effectiveness, compliance and relevance of the policy

way in: Mission, objectives and stakeholder expectations

  1. L1: The organisation's mission, strategic and performance plans, and what internal and external stakeholders expect
  2. L2: Mission understood and informing cybersecurity risk management (GV.OC-01, -02)
  3. L3: Purpose and goals of the program: integrity, availability or confidentiality stressed according to what the organisation does

way in: Risk assessment results

  1. L1: The organisation's current cybersecurity risks: assets, suppliers and threats (IDENTIFY)
  2. L2: Risk assessment results received as an input (assessing risk belongs to risk management, not policy development)
  3. L3: Security requirements derived from the assessed risks

way in: Security incidents and incident reports

  1. L1: Security incidents in the organisation
  2. L2: Incident reports gathered for the policy review
  3. L3: Number and type of incidents read as indicators of where the policy is no longer effective

way in: Standards and frameworks (ISO/IEC 27001/27002, NIST CSF, SP 800-53, COBIT)

  1. L1: Published generic requirements and reference control sets (93 Annex A controls; 106 CSF subcategories)
  2. L2: A framework adopted; Current and Target Organizational Profiles drawn
  3. L3: Controls selected and gaps analysed into an action plan (risk register, POA&M); policy controls are the '-1' control of each SP 800-53 family

way in: Suppliers and third parties

  1. L1: Suppliers, their products and services, and other third parties
  2. L2: Suppliers known and prioritised by criticality; due diligence before the relationship (GV.SC-04, -06)
  3. L3: Supplier risks understood, recorded, prioritised, assessed and monitored over the relationship (GV.SC-07)

way out: Assign roles and allocate resources

  1. L1: People in offices with budget, staff and authority
  2. L5: Adequate resources allocated commensurate with strategy, roles and policies; cybersecurity included in HR practices
  3. L7: Executives communicate expectations about accountability and resources

way out: Bind suppliers by contract

  1. L1: Suppliers' roles and responsibilities established, including after the agreement ends
  2. L3: Integrated into contracts and other agreements; Target Profile expressed to suppliers
  3. L4: Requirements for supply-chain risk established and prioritised

way out: Discipline and penalties for violations

  1. L1: Penalties and disciplinary actions on the member
  2. L3: Violation weighed by the act, its severity and the user's intent
  3. L5: Compliance structures authorised, an office tasked with monitoring compliance; coordinated with officials and bargaining units

way out: Distribute and communicate the policy (documents, briefings, SETA, campaigns)

  1. L1: Members made aware of the policy, its reasons, how it affects them and what follows if they do not comply
  2. L3: Delivery methods chosen (print, email, intranet, HTML or PDF); communicated through briefings, seminars and awareness campaigns
  3. L4: Policy approved and published

way out: Enforce through mechanisms (access control, patching, monitoring, policy as code)

  1. L1: Constraints on functions, flows and access in the organisation's systems
  2. L3: Technological mechanisms implemented: user administration, security patches, monitoring for security events, anti-virus; rules written as code checked by tools
  3. L4: System-specific policy: operational security rules detailed enough to tell when a violation occurred

way out: Report and assure outward (FISMA reports, certification, disclosure)

  1. L1: Regulators, oversight bodies, customers and partners told the organisation's security state (a Current Profile can be shared with business partners)
  2. L3: Results reported to OMB, which reports to Congress; ISMS certified by an independent body
  3. L6: Annual reviews of the security program by program officials, CIOs and inspectors general

Who fills each layer

Sources (28) published science

NIST, The NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29, 26 February 2024 (doi:10.6028/NIST.CSWP.29)
Security policy (encyclopedia)
Wong (2022). A Process Model to Improve Information Security Governance in Organisations. PhD thesis, University of Melbourne. arXiv:2302.01753 (behind its links)
Alshaikh, Maynard, Ahmad & Chang (2015). Information Security Policy: A Management Practice Perspective. ACIS 2015. arXiv:1606.00890 (behind its links)
Ertan, Crossland, Heath, Denney & Jensen (2018). Everyday Cyber Security in Organisations: literature review. Royal Holloway. arXiv:2004.11768 (behind its links)
ISO/IEC 27001 (encyclopedia) (behind its links)
Lee, Lallie & Michaelides (2023). The impact of an employee's psychological contract breach on compliance with information security policies: intrinsic and extrinsic motivation. arXiv:2307.02916 (behind its links)
Federal Information Security Management Act of 2002 (encyclopedia) (behind its links)
NIST (2024). The NIST Cybersecurity Framework (CSF) 2.0. NIST CSWP 29. doi:10.6028/NIST.CSWP.29 (behind its links)
Nieles M, Dempsey K, Pillitteri VY (2017) NIST SP 800-12 Rev. 1: An Introduction to Information Security. doi:10.6028/NIST.SP.800-12r1 (behind its links)
Bowen, Hash & Wilson (2006). NIST SP 800-100, Information Security Handbook: A Guide for Managers (ch. 2, Information Security Governance) (behind its links)
Corporate governance of information technology (encyclopedia) (behind its links)
Bell–LaPadula model (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Chief information security officer (encyclopedia) (behind its links)
NIS2 Directive (encyclopedia) (behind its links)
Adomako, Mumuni, Akoto & Koranteng (2026). Exploring the Drivers of Information Security Policy Compliance Among Contingent Employees. arXiv:2603.07208 (behind its links)
Shreeve, Hallett, Edwards, Ramokapane, Atkins & Rashid (2021). The best laid plans or lack thereof: Security decision-making of different stakeholder groups. arXiv:2104.00284 (behind its links)
Sari, Handayani, Hidayanto, Yazid & Aji (2022). Information Security Behavior in Health Information Systems: A Review of Research Trends and Antecedent Factors. Healthcare 10(12):2531. doi:10.3390/healthcare10122531 (PMC9777837) (behind its links)
Foalem, Khomh, Da Silva & Merlo (2026). An Empirical Study of Policy-as-Code Adoption in Open-Source Software Projects. arXiv:2601.05555 (behind its links)
Jensen & Da Silva (2022). 'Cyber security is a dark art': The CISO as soothsayer. arXiv:2202.12755 (behind its links)
Separation of duties (Wikipedia, via Wikimedia Enterprise) (behind its links)
Information security audit (encyclopedia) (behind its links)
Swanson M, Bowen P, Phillips AW, Gallup D, Lynes D (2010). NIST SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems. doi:10.6028/NIST.SP.800-34r1 (behind its links)
Common Criteria for Information Technology Security Evaluation, Part 3: Security assurance components, Version 3.1 Revision 5 (2017) (behind its links)
Onibere (2026). Dual-Fit Imperative in Security Leadership: A Grounded Theory Investigation of CISO Role Enactment in Modern Organisations. PhD thesis. arXiv:2609.35887 (behind its links)
Alencar, de Moura, de Farias Junior & Teixeira Filho (2018). An Adaptable Maturity Strategy for Information Security. arXiv:1807.06184 (behind its links)
Biba Model (encyclopedia) (behind its links)
Clark-Wilson model (encyclopedia) (behind its links)