|  CASE STUDY · INFORMATION SECURITY · POLICIES AND STANDARDS

How an IT organisation turns its security handbook into something you can ask

The security handbook, policies and standards sit as PDFs on the intranet, and the external guidance keeps changing. KnowledgeHub turns them into something staff and coding assistants can ask, and the answer comes with its source.

The answer comes with its source.

|  The problem

The rules don't get read

The security handbook, policies, architecture principles and standards are PDFs on the intranet. They are rarely read when a member of staff has to make a choice or a developer has to set up a system.

Meanwhile the external guidance keeps changing, for example the NIS 2 guidance from SAMSIK and sikkerdigital.dk. Questions land with a few specialists, who answer the same ones again and again.

01

Ask in chat or search

Staff get the current answer, cited to the rule it rests on.

02

Looked up as code is written

Coding assistants such as GitHub Copilot, Claude Code and Cursor look up the rules via MCP server or API.

03

Mismatches flagged

KnowledgeHub flags when an internal rule and an external guideline don't match.

|  Inside the developer's day

Two questions, neither for the specialists

01 · Morning

A configuration to write

A developer at a supplier has to set up logging on a new solution for the agency.

The developer asks the coding assistant to write the configuration.

Coding assistant
02 · Lookup

The rule, before the code

The coding assistant looks up KnowledgeHub before it writes.

It gets the agency's requirements for logging and retention from the security handbook, cited to the section, and writes the configuration to match.

MCP server
03 · Review

Each choice with its rule

The developer can see which rule each choice rests on.

Code and configuration are checked against the standards as they are written, where flaws are cheapest to fix.

Security handbook
04 · Same day

An answer from the policy

Someone in a policy office asks in chat whether a type of document may be shared with an external partner.

The answer comes from the policy, with its source. The specialists keep their time for the questions that need judgement.

Policy
|  What changed

Rules used where the work happens

  • Fewer repeat questions to the specialists.
  • The handbook is looked up when a choice is made and when code is written.
  • Fewer security flaws early in development.
  • When external guidance changes, it's clear where the internal rules need to follow.
Sector
Public sector
Region
Denmark
Org scale
Ministries, agencies and regions
Personas
Staff, developers and suppliers, CISO, information security coordinator, head of IT and architecture
Products
KnowledgeHub · Case workspace · Graph traversal · Agents
Compliance
GDPR-aligned processing · ISO 27001 posture · configurable retention
|  Use cases

More from Public sector

|  Next step

Easy to start. Safe to stop.

The pilot runs at a fixed price: we map the workflow, deploy it in your environment and prove it on your own cases. Then you decide.

Fixed price · Fixed timeframe

  1. 01

    Map the workflow

    Two weeks with your people where we document what happens today, including the parts nobody wrote down.

  2. 02

    Deploy in your environment

    Inside your tenancy, on your data residency terms, with no exports and nothing leaving through the side door.

  3. 03

    Prove it under audit

    Controlled evaluation against your own cases with compliance and the process owner signing off before go-live.

  4. 04

    Run in production

    We stay on with retraining, reporting and ongoing oversight for as long as the workflow runs.

Fixed price, Fixed timeframe. 8–12 weeks pilot: Continue (Expand once you know it works) / Stop.