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 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.
And a new kind of user has arrived: AI coding assistants that write code and configuration. They don't know the organisation's rules.
KnowledgeHub ingests the security handbook, policies, architecture principles and standards together with the NIS 2 guidance from SAMSIK and sikkerdigital.dk and the relevant legislation from Retsinformation. The external sources are maintained, so the answer follows the current guidance.
Staff ask in chat or search and get the current answer, cited to the rule it rests on. Coding assistants look up the same rules via KnowledgeHub's MCP server or API, so code and configuration can be checked against the standards as they are written. Where an internal rule and an external guideline don't match, it is flagged.
The answers are measured against a test set built with the CISO function, so the organisation can see that they are right.
Ask in chat or search
Staff get the current answer, cited to the rule it rests on.
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.
Mismatches flagged
KnowledgeHub flags when an internal rule and an external guideline don't match.
Two questions, neither for the specialists
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.
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.
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.
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.
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
More from Public sector
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
- 01
Map the workflow
Two weeks with your people where we document what happens today, including the parts nobody wrote down.
- 02
Deploy in your environment
Inside your tenancy, on your data residency terms, with no exports and nothing leaving through the side door.
- 03
Prove it under audit
Controlled evaluation against your own cases with compliance and the process owner signing off before go-live.
- 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.