Cybersecurity
Information security program development and governance
Security governance turns good intentions into a program that runs. We design the program, write the policy framework, set up the risk and metrics reporting your leadership reads, and build the process for assessing suppliers, on ISO/IEC 27001 and NIST CSF.
Overview
Most companies have pieces of a security program: a policy written for a customer questionnaire, a risk spreadsheet from an old audit, a supplier check that depends on one person remembering to do it. Information security program development connects those pieces into something that runs on its own, with owners, a schedule and evidence. That is what this service sets up, and, if you want, keeps running with you.
Who it suits
This service suits companies whose security has grown faster than the structure around it. Common triggers are a board or investor asking how security risk is managed, a large customer sending a security questionnaire the company struggles to answer, a first security hire who needs a program to run, or a plan to seek ISO/IEC 27001 or SOC 2 in the next year or two.
It suits companies of different sizes, because the program is sized to the company. What changes is how much is written down and how often it is reviewed, not whether there is an owner and a plan.
What a security program contains
A security program is more than its policies. It names who is accountable for security and who owns each risk. It sets out which policies and standards apply and how exceptions are approved. It keeps a risk register that is reviewed on a schedule, and it reports a few measures to leadership so that progress can be seen over time. It checks suppliers in proportion to the risk they carry, because many breaches start with a supplier.
We build each of these parts on ISO/IEC 27001 and NIST CSF. ISO/IEC 27001 gives the program the structure of a management system, with a cycle of planning, doing, checking and improving. NIST CSF gives a common language for the controls and for reporting to people outside the security team. Using both keeps the program recognisable to auditors and customers without tying it to any single certificate.
Policies people can follow
Policies fail when they are too long to read or too vague to apply. We write each one for your company: what it requires, who it applies to, who owns it and when it is next reviewed. Where a policy needs a procedure to work, such as how access is granted or how a supplier is assessed, the procedure is written alongside it and tried out with the people who will use it.
Set-up, then a retainer if you want one
The set-up takes two to four months at a fixed price and ends with the program running: policies approved, the risk register in use, the first report delivered and the supplier process applied to your existing suppliers. After that, a monthly retainer keeps it current. You can keep us on while your own team grows, or take the program over at the end of the set-up. Either way, the decisions stay with your company.
Deliverables
What you get
- Security program design
The structure of your security program, including who owns what, how decisions are made and recorded, what the program covers and in which order the gaps are closed, based on ISO/IEC 27001 and NIST CSF.
- Policy framework
A set of security policies and standards written for your company, in plain language, with an owner and a review date for each, and the procedures that make them work in practice.
- Risk and metrics reporting
A risk register and a short set of measures your leadership and board can follow over time, reported on a regular schedule, so that security decisions are made on evidence rather than on the latest headline.
- Third-party risk process
A way to assess suppliers before you sign and to review them afterwards, with questionnaires sized to the risk each supplier carries and a record of what was checked and decided.
Process
How an engagement runs
- 01
Understand where you are
We review what already exists, such as policies, risk records, audit findings and customer requirements, and talk to the people who own security today, so that the program builds on what works.
- 02
Design the program
We agree the program's scope, roles and decision-making with your leadership, map it to ISO/IEC 27001 and NIST CSF, and set the order in which gaps will be closed.
- 03
Write the policies and processes
Policies, standards and procedures are drafted, reviewed with their owners and approved. The third-party risk process is set up with its questionnaires and records.
- 04
Start the reporting
2 to 4 months for the set-up
The risk register and the measures go live, and the first report is produced with your team, so the cycle is running before the set-up ends.
- 05
Keep it current
After the set-up, a monthly retainer keeps the program current. We maintain the policies, update the risk register, prepare the reports and help with supplier reviews, with your team owning the decisions.
FAQ
Frequently asked questions
How is security governance different from compliance and certification?
Compliance and certification prepare you to pass a particular audit, such as ISO/IEC 27001 or SOC 2. Governance is the program that makes security run every day, whether or not an audit is coming. It settles who owns which risk, which policies apply, what leadership sees at each review and how suppliers are checked. A good program makes certification much easier, and many companies do both, but we sell them separately because not every company needs a certificate.
Who is accountable for security once the program is running?
Someone inside your company. We design the program, set up its reporting and, on a retainer, keep it current, but the decisions and the accountability stay with you. Part of the set-up is naming that owner and writing down what they decide and approve, so the program has someone who can answer for it to the board, to customers and to auditors.
Which framework should our program follow?
We usually build on ISO/IEC 27001 for the structure of the management system and NIST CSF for the language of the controls and the reporting, because the two fit together well and most customers and auditors recognise them. If a certification is likely later, building on ISO/IEC 27001 from the start saves rework.
What do the board and leadership receive?
A short regular report built from the risk register and a few measures chosen with them, showing the main risks, how they are changing, what was decided and what is overdue. It is written for people who are not security specialists, and it is the same format each time so trends are easy to see.
We are a small company. Is this too much for us?
The program is sized to the company. A small company needs a few clear policies, one owner, a simple risk register and a basic supplier check, not a library of documents nobody reads. We scope the set-up to what your size, customers and regulators require, and the retainer can be light or stopped once your own team is ready.
Related
Related services
Compliance & Certification
ISO/IEC 27001 consulting and SOC 2 readiness: a gap assessment, the policies and controls you lack, audit preparation and ongoing compliance upkeep.
ExploreThreat Detection & SIEM Implementation
SIEM implementation on Microsoft Sentinel, Splunk, Elastic Security or Wazuh, with log sources, detection rules and runbooks handed to your team.
ExploreRed Teaming & Penetration Testing
Penetration testing services for web apps, APIs, networks, cloud and Active Directory, plus red teaming. Every test ends with a report and a retest.
ExploreThe engagement
- Duration
- 2 to 4 months to set up; then monthly
- Pricing
- Monthly retainer
The set-up is fixed price, agreed in the scope before work starts. Keeping the program current afterwards is a monthly retainer.
- ISO/IEC 27001
- NIST CSF
Next step
Tell us where your security program stands
A few lines on what exists today and what prompted the question are enough. We reply within two business days.