Security teams are often held accountable for outcomes they have no authority to deliver, because nobody wrote down what the security function is for, what it covers and what it may require of others. A programme charter is that document: a short, executive-approved mandate that gives the security function its purpose, scope, authority, reporting line, resources and measures. It is different from a governance committee charter, which defines how a decision-making forum works; the programme charter defines the function that the committee oversees. NIST CSF 2.0 expects leadership to be accountable for cybersecurity risk (GV.RR-01) and roles, responsibilities and authorities to be established and enforced (GV.RR-02), NIST SP 800-53 Rev. 5 control PM-1 calls for an information security programme plan, and the UK Cyber Governance Code of Practice (published 8 April 2025) asks boards to embed a cyber governance structure with clear roles (E1). This template is for CISOs, chief information officers and executive sponsors writing or renewing a charter. For the committee document see the Security Governance Committee Charter Template.
How to use this template
- Replace text in square brackets, such as [Organisation], [Chief Information Security Officer] and [Executive sponsor], with your own terms.
- "Must" indicates a mandatory requirement; "should" indicates a recommended practice where a justified exception may apply.
- Keep the charter to four to six pages. Detailed standards, procedures and the roadmap sit in separate documents that the charter authorises.
- The charter should be approved by the chief executive or executive committee and noted by the board or its risk committee. Approval below that level weakens the authority in section 3.
- Agree the reporting line (section 4) before drafting anything else; it shapes independence, budget and escalation.
1. Purpose and mandate
The [Information Security function] ("the Security Function") is established by [Chief Executive Officer / Executive Committee] to protect [Organisation]'s information, systems, services and the identities that access them, so that the organisation can pursue its objectives within the cyber risk appetite approved by the [Board of directors]. The Security Function must:
- Maintain and deliver a security strategy aligned with the organisation's strategy and risk appetite.
- Identify, assess and report cyber risk, and advise risk owners on treatment.
- Set security policy and standards, and monitor compliance with them.
- Operate or oversee the security capabilities listed in section 6.
- Lead the response to cyber security incidents in coordination with the business.
- Provide management and the board with accurate information on cyber risk and security performance.
Accountability for business risk remains with risk owners. The Security Function advises, sets requirements, operates agreed capabilities and reports; it does not own every security risk.
2. Scope
The mandate applies to [Organisation] and all subsidiaries and controlled entities, including:
- All information, in any format, created, processed or held by or for the organisation.
- All technology: on-premises, cloud, SaaS, operational technology, end-user devices and development pipelines.
- All identities: workforce, contractors, customers where managed by the organisation, and non-human identities such as service accounts, API keys, tokens, certificates, workloads and AI agents.
- Third parties that process the organisation's data or connect to its systems, to the extent defined in contracts.
- New products, acquisitions, divestments and major change programmes.
Out of scope: [physical security / fraud / business continuity / privacy compliance], which are owned by [named function]. Interfaces with those functions are defined in section 10.
3. Authority
To carry out this mandate, the [Chief Information Security Officer] and authorised delegates are empowered to:
- Issue security policies once approved under the policy framework, and issue standards and procedures under their own authority.
- Have timely access to all systems, records, logs, configurations and personnel needed to assess risk, investigate incidents or verify compliance, subject to legal and privacy requirements.
- Require that new systems, suppliers and changes complete security review before production use, at the thresholds set in [Security review standard].
- Direct emergency containment actions during a declared incident, including disabling accounts or credentials, isolating systems and blocking network traffic, informing the system owner as soon as practicable.
- Approve, reject or escalate requests for exceptions to security policy, within the limits in section 11.
- Commission independent testing, including penetration tests and red team exercises, under the rules of engagement in [Testing standard].
- Escalate unresolved risk or non-compliance directly to [Executive sponsor] and, where needed, to [Board risk committee].
4. Accountability and reporting lines
| Relationship | Arrangement |
|---|---|
| Line reporting | [CISO] reports to [Chief Executive Officer / Chief Operating Officer / Chief Risk Officer] |
| Governance reporting | [CISO] reports to [Security governance committee] at least [monthly] |
| Board access | [CISO] attends [Board risk committee] at least [quarterly] and has the right to request a private session with its chair |
| Independence safeguard | Where the CISO reports into the technology function, the CISO may escalate to [Chief Risk Officer] without the line manager's approval |
The Cyber Governance Code of Practice asks boards to require formal reporting at least quarterly with metrics and agreed tolerances (E2) and to maintain regular two-way dialogue with senior executives, including the CISO (E3). The arrangements above should make both possible.
5. Roles and responsibilities
- [Board of directors]: approves cyber risk appetite, oversees cyber risk and receives assurance.
- [Executive sponsor]: approves this charter, champions the programme and resolves cross-functional conflicts.
- [Chief Information Security Officer]: leads the Security Function, owns the security strategy, policy framework and security risk reporting.
- Risk owners and business leaders: own the cyber risks in their area, fund treatment and accept residual risk within their delegated authority.
- Technology and engineering leaders: implement and operate security controls in the platforms they own.
- All staff and contractors: follow security policy and report incidents and suspected weaknesses.
- Owners of non-human identities: each service account, API key, workload identity and AI agent has a named human owner accountable for its access and credentials.
- Internal audit: provides independent assurance over the programme and is not directed by the Security Function.
A detailed assignment by activity sits in the Security RACI Matrix Template.
6. Programme objectives and capabilities
The Security Function maintains a [three]-year strategy and annual plan. Capabilities in scope, with the delivery model for each:
| Capability | Delivery model | CSF 2.0 Function |
|---|---|---|
| Security governance, risk and policy | [In-house] | Govern |
| Asset, vulnerability and threat management | [In-house with managed scanning] | Identify |
| Identity and access security, including non-human identities | [Shared with IAM team] | Protect |
| Security architecture and engineering | [In-house] | Protect |
| Security monitoring and detection | [Managed SOC with in-house oversight] | Detect |
| Incident response | [In-house with retained provider] | Respond |
| Recovery support and resilience testing | [Shared with IT operations] | Recover |
| Awareness, training and culture | [In-house] | Govern, Protect |
| Third-party security risk | [Shared with procurement] | Govern |
7. Resourcing and budget
- The Security Function holds its own budget line, approved annually by [Executive committee], covering staff, tools, managed services and testing.
- Security controls embedded in business or technology platforms are funded by the platform owner unless agreed otherwise.
- Resourcing must be proportionate to the cyber risk strategy, consistent with CSF 2.0 GV.RR-03 and Cyber Governance Code action B3. Material shortfalls are reported to [Security governance committee] as a risk.
- Workforce planning, skills and training needs are reviewed annually (SP 800-53 PM-13).
See the Security Budget Template.
8. Policy framework
The Security Function maintains a tiered framework: policies approved by [Executive committee], standards approved by the CISO, and procedures owned by operating teams. Policies are reviewed at least [annually] and after significant changes in requirements, threats or technology (GV.PO-02). See the Security Policy Framework Guide.
9. Performance measurement and reporting
The Security Function reports at least [quarterly] against a small set of measures agreed with [Security governance committee], for example:
- Top cyber risks against tolerance, with trend.
- Strategy and roadmap delivery against plan.
- Critical vulnerabilities remediated within target.
- Coverage of privileged and non-human identities with a named owner.
- Incident volumes, mean time to contain, and lessons-learned actions closed.
- Policy exceptions open and past expiry.
See the Security Metrics and KPIs Programme Guide.
10. Relationships with other functions
| Function | Interface |
|---|---|
| Enterprise risk management | Cyber risks are recorded in the enterprise risk register using the shared methodology |
| Privacy and data protection | Joint assessment of incidents involving personal data; shared breach notification decision process |
| Legal and compliance | Regulatory interpretation, contract clauses, disclosure decisions |
| Business continuity | Cyber scenarios included in continuity plans and exercises |
| Procurement | Security requirements in sourcing and supplier onboarding |
| Human resources | Joiner, mover and leaver controls; disciplinary process for policy breaches (GV.RR-04) |
| Internal audit | Independent assurance; findings tracked to closure by the owning function |
11. Exceptions and escalation
- Exceptions to policy must be requested by the risk owner, assessed by the Security Function and time limited to a maximum of [12] months.
- The CISO may approve exceptions rated [medium] or below. Exceptions rated [high] require [Executive sponsor] approval; those outside risk appetite require [Security governance committee] approval.
- Disagreements between the Security Function and a business or technology leader that cannot be resolved within [10] business days are escalated to [Executive sponsor].
12. Review and approval
This charter is reviewed at least every [two] years, and after a change in reporting line, a major reorganisation, an acquisition or a significant incident.
| Version | Date | Approved by | Summary of change |
|---|---|---|---|
| [1.0] | [Date] | [Chief Executive Officer] | [Initial charter] |
Implementation guidance
- Draft with the sponsor, not for them. Agree purpose, scope and reporting line in one working session with the executive sponsor before writing; a charter written in isolation is usually rejected or diluted.
- Test the authority clauses. Walk through three real cases (an urgent account disablement, a supplier that refuses an assessment, a project that bypassed review) and check that sections 3 and 11 give a clear answer.
- Consult the functions in section 10 and record their agreement, so the interfaces are accepted rather than imposed.
- Publish and brief. Publish the approved charter on the intranet and brief senior leaders; authority nobody knows about cannot be used.
- Small organisations: a two-page charter with sections 1 to 4 and 11 is enough where security is one person or an outsourced service. Name the accountable executive and the provider's authority explicitly.
- Large organisations: keep one group charter and short divisional addenda that may narrow, but not widen, the delegated authorities.
- Measure adoption: track charter review date, number of escalations under section 11, and percentage of projects completing security review before go-live.
Common failure patterns: a charter approved only by the CIO, so the CISO lacks authority over other business lines; scope silent on cloud, SaaS or machine identities; no independence safeguard where security reports into technology; and authority clauses that never mention incidents, so containment waits for owner approval.
| Charter section | NIST CSF 2.0 | NIST SP 800-53 Rev. 5 | Cyber Governance Code |
|---|---|---|---|
| 1 Purpose, 6 Objectives | GV.RM-01, GV.OC-02 | PM-1 Information Security Program Plan | B1, B2 |
| 3 Authority, 5 Roles | GV.RR-01, GV.RR-02 | PM-2, PM-29 | A2, E1 |
| 4 Reporting lines, 9 Measures | GV.RM-05, GV.OV-02 | PM-6 Measures of Performance | E2, E3 |
| 7 Resourcing | GV.RR-03 | PM-3, PM-13 | B3 |
| 8 Policy framework | GV.PO-01, GV.PO-02 | PM-1 | C2 |
| 10 Internal audit interface | GV.OV-03 | PM-14 Testing, Training, and Monitoring | E4 |
Standards and references
- NIST: Cybersecurity Framework 2.0
- NIST: SP 800-53 Rev. 5
- UK Government: Cyber Governance Code of Practice
- NIST: IR 8286 Rev. 1, Integrating Cybersecurity and Enterprise Risk Management
This template is provided for guidance and must be adapted to your organisation. Related NHI Mgmt Group resources: Security Governance Committee Charter Template · Security Programme Building Guide · CISO Guide: First 90 Days · Security Programme Maturity Assessment Template