← 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 at | contested (see C-1732) |
| born precision | contested |
| boundary | Inside: 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 level | A 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. |
| scale | social |
Measures (22) published science
| characteristic clock: policy review cycle | at least 1 per year |
| ISO/IEC 27001 surveillance audit interval | first within 12 months, then at least once each calendar year |
| ISO/IEC 27001 recertification cycle | 3 years |
| FISMA program review | 1 per year |
| US agency strategic plan refresh (GPRA) | within 3 years |
| NIST CSF 2.0 Core size | 6 Functions, 22 Categories, 106 Subcategories count |
| NIST CSF 2.0 GOVERN size | 6 Categories, 31 Subcategories count |
| ISO/IEC 27001:2022 Annex A controls | 93 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 fines | EUR 10 million or 2% of worldwide turnover (essential); EUR 7 million or 1.4% (important) EUR / % |
| psychological contract breach -> ISP compliance intention | path coefficient -0.195, p = 0.002, n = 206 UK employees PLS path |
| contingent staff: attitude -> compliance intention | beta = 0.586, f2 = 0.376, n = 688 PLS path |
| contingent staff: knowledge sharing -> attitude | beta = 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 game | 208 sessions, 948 players; 30% of teams went bust; no background significantly better count |
| health ISB studies on policy and regulation compliance | 17 (of 25 on desired security behaviour) studies |
| policy management practices | 7 practices in 3 stages, from 112 papers (1994-2015) count |
| policy-as-code study size | 399 repositories, 9 tools; DevOps infrastructure 17% of projects count |
| first CISO title | 1995 year |
Open contentions (5) open contention
Where sources or readings disagree. Both stay on the map.
- C-1697 Does security certification make organisations more secure?
booked: The map counts certification as a route to assurance and leaves its effect on security open, since few studies have measured it.
the other reading: certification provides independent assurance of conformity; a 2021 systematic review found few studies had examined outcomes of certification empirically - C-1699 Who should the chief security officer report to?
booked: The map books the shift away from reporting to the chief information officer and keeps the view that the right line depends on the organisation.
the other reading: CISO under the CIO is suboptimal: conflict of interest, role wider than IT; the right line varies with size, industry, regulation and risk profile; the role is continuously negotiated with its context - C-1712 Do penalties or shared values make staff follow security rules?
booked: The map books both readings.
the other reading: deterrence works: certainty of detection and severity of punishment significantly shape attitudes (contingent staff, beta 0.287 and 0.313); sanction severity and certainty not significant for deviant behaviour compared with planned-behaviour factors (review cited by Lee et al.); shift from incentives and sanctions toward a shared vision; security culture improves compliance; top-down, policy-based approaches found ineffective by some studies; heavy-handed enforcement breeds tension and shadow security - C-1727 What does 'security policy' mean?
booked: The map keeps both senses: an organisation's rules for people, and the formal models that define allowed access.
the other reading: policy as 'statements, rules or assertions that specify the correct or expected behavior of an entity' (SP 800-95 via SP 800-12); policy as managerial decisions about how the organisation manages, protects and distributes information - C-1732 When did security policy begin?
booked: The map leaves it contested: rules as old as locks and accounting, formal models from 1973, or governance named in 2013.
the other reading: organisational rules for security as old as locks, walls and accounting's separation of duties; formal computer security policy (Bell-LaPadula 1973); information security governance as a named practice (ISO/IEC 27014 2013; CSF GOVERN 2024)
Partners and parts published science
Built from / builds (9)
- Computer security
- Human (Homo sapiens)
- Chief information security officer
- Program policy
- Issue-specific policy
- System-specific policy
- Governance processes: direct, monitor, evaluate, communicate, assure
- Security against business enablement for priority and resources
- Compliance demands against members' productive work
Sits inside / holds (6)
- Computer security
- Information security
- Organization
- Corporate governance (IT governance as its subset)
- Formal security policy model
- Security audit and compliance
Trades with (valence) (16)
- Human (Homo sapiens) via sys:human · Security policy and governance gain
- Law (rules and law) via sys:law · Security policy and governance mixed
- Computer security via sys:organization · Security policy and governance gain
- Access control via sys:information-system · Security policy and governance gain
- Incident response via sys:incident-response · Security policy and governance gain
- Information security via sys:organization · Security policy and governance gain
- Risk management via sys:risk-management · Security policy and governance gain
- Insider threat via sys:human · Security policy and governance mixed
- Organization via sys:organization · Security policy and governance gain
- Supply chain security via sys:supply-chain-security · Security policy and governance gain
- Business continuity via sys:written-record · Security policy and governance gain
- Security standard via sys:security-standard · Security policy and governance gain
- Information security audit via sys:information-security-audit · Security policy and governance mixed
- Security awareness via sys:human · Security policy and governance gain
- Formal security policy model via sys:security-policy · Security policy and governance gain
- Security audit and compliance via sys:organization · Security policy and governance gain
expressed by (17)
- Templating / Standardization
- Encapsulation & Modularity (Abstraction)
- Evolvability/Plasticity Engineering (Design for Future Variation)
- Distributed Autonomy/Decentralized Execution (Subsidiarity)
- Internal Coordination/Regulation
- Sensing/Scanning
- Hypothesis/Goal Selection
- Multi-Scale Data Fusion / Triangulation
- Trail-Marking / Externalized Memory (Stigmergy)
- Surprise / Change-Point Detection
- Social Learning / Public Information Use
- Proactive Defense
- Self-Monitoring
- Validation of Effectiveness
- Triage & Prioritized Allocation
- Deterrence
- Quality Control & Error Correction
floor filled by (16)
- Computer security
- Human (Homo sapiens)
- Law (rules and law)
- Threat actor
- Risk management
- Organization
- Chief information security officer
- Program policy
- Issue-specific policy
- System-specific policy
- Governance processes: direct, monitor, evaluate, communicate, assure
- Security standard
- Information system
- Information security audit
- Board of directors
- Security audit and compliance
Kinds (4)
Notes published science
- NIST tells organisations to name policy contacts by position, not by person, 'since positions tend to change less often than the individuals occupying them': a security policy builds its doors into the org chart before anyone knocks (src:nist-sp800-12r1).
- Biba's integrity model is Bell-LaPadula run backwards: one protects secrets with 'read down, write up', the other protects orders with 'read up, write down', and its first two rules are literally 'the reverse of the Bell-LaPadula rules' (src:wp:biba-model).
- In a security investment game played by 948 people in 208 sessions, no group (board members, CISOs, risk analysts, security experts) made significantly better decisions than anyone else, and 30% of teams went bust (src:shreeve-2021-decisions).
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)
- 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)
- L2: Organisational context taken in: mission, stakeholder expectations, dependencies, and legal, regulatory and contractual requirements understood (GV.OC); security needs determined
- L3: Security requirements identified: what the organisation must achieve, from risk assessment results, existing policies and outside requirements; security objectives commensurate with risk
- L4: The policy set: program, issue-specific and system-specific policy, with organisational standards, guidelines and procedures under them; drafted, reviewed and approved
- L5: Roles, responsibilities and authorities: leadership accountable, CISO/SAISO, offices, resources allocated; a centralised, decentralised or hybrid structure
- L6: Oversight: monitor and evaluate (management review, internal audit, metrics), strategy reviewed and adjusted; risk appetite and tolerance held
- 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)
- 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
- L5: Roles, responsibilities and authorities: leadership accountable; the CISO or SAISO directing the program; offices and resources assigned; structure centralised, decentralised or (usually) hybrid
- L6: Oversight: monitor (check compliance) and evaluate (compare with objectives, decide changes); management review, internal audit, metrics; the CISO interprets for senior management
- 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)
- L1: System records, activities and related documents examined independently
- L2: Internal audits and management reviews at planned intervals; external surveillance audits
- L3: Nonconformities found and corrective action required
way in: Laws, regulations and contracts (FISMA, NIS2, GDPR, PCI DSS, contracts)
- L1: Laws, regulations and directives that establish responsibilities, minimum controls and compliance reporting
- L2: Legal, regulatory and contractual requirements understood and managed (GV.OC-03); legal counsel consulted on penalties
- L3: Balanced against agency-specific policy, which may be more stringent than the law
way in: Members' conduct and feedback (compliance, workarounds, attitudes)
- L1: What members actually do under the policy: comply, violate unintentionally, or work around it (shadow security)
- L2: Feedback collected from managers and users by interviews and surveys; compliance monitored
- L3: Feedback analysed for effectiveness, compliance and relevance of the policy
way in: Mission, objectives and stakeholder expectations
- L1: The organisation's mission, strategic and performance plans, and what internal and external stakeholders expect
- L2: Mission understood and informing cybersecurity risk management (GV.OC-01, -02)
- L3: Purpose and goals of the program: integrity, availability or confidentiality stressed according to what the organisation does
way in: Risk assessment results
- L1: The organisation's current cybersecurity risks: assets, suppliers and threats (IDENTIFY)
- L2: Risk assessment results received as an input (assessing risk belongs to risk management, not policy development)
- L3: Security requirements derived from the assessed risks
way in: Security incidents and incident reports
- L1: Security incidents in the organisation
- L2: Incident reports gathered for the policy review
- 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)
- L1: Published generic requirements and reference control sets (93 Annex A controls; 106 CSF subcategories)
- L2: A framework adopted; Current and Target Organizational Profiles drawn
- 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
- L1: Suppliers, their products and services, and other third parties
- L2: Suppliers known and prioritised by criticality; due diligence before the relationship (GV.SC-04, -06)
- L3: Supplier risks understood, recorded, prioritised, assessed and monitored over the relationship (GV.SC-07)
way out: Assign roles and allocate resources
- L1: People in offices with budget, staff and authority
- L5: Adequate resources allocated commensurate with strategy, roles and policies; cybersecurity included in HR practices
- L7: Executives communicate expectations about accountability and resources
way out: Bind suppliers by contract
- L1: Suppliers' roles and responsibilities established, including after the agreement ends
- L3: Integrated into contracts and other agreements; Target Profile expressed to suppliers
- L4: Requirements for supply-chain risk established and prioritised
way out: Discipline and penalties for violations
- L1: Penalties and disciplinary actions on the member
- L3: Violation weighed by the act, its severity and the user's intent
- 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)
- L1: Members made aware of the policy, its reasons, how it affects them and what follows if they do not comply
- L3: Delivery methods chosen (print, email, intranet, HTML or PDF); communicated through briefings, seminars and awareness campaigns
- L4: Policy approved and published
way out: Enforce through mechanisms (access control, patching, monitoring, policy as code)
- L1: Constraints on functions, flows and access in the organisation's systems
- L3: Technological mechanisms implemented: user administration, security patches, monitoring for security events, anti-virus; rules written as code checked by tools
- 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)
- L1: Regulators, oversight bodies, customers and partners told the organisation's security state (a Current Profile can be shared with business partners)
- L3: Results reported to OMB, which reports to Congress; ISMS certified by an independent body
- L6: Annual reviews of the security program by program officials, CIOs and inspectors general