Live demonstration on request

Comply once. Prove everything.

ControlGraph holds the frameworks an organisation answers to, their controls, and every approved relationship between them as one governed map. When PISF, ISO 27001 and a sector rule ask for the same thing, you do the work once and see everywhere it counts, with the source and the approver of every link on record.

ControlGraph · Relationship explorerDemo environment
The ControlGraph relationship explorer, tracing one CIS control to its related controls in SOC 2, ISO/IEC 27001, NIS2, NIST SP 800-53, PCI DSS and the CIS Controls themselves, grouped by framework
Real product screen, sample dataAzbersInnovations

The question every auditor asks, answered on one screen. What else does this control satisfy? Screen from the ControlGraph demonstration environment.

In the catalogue of the demonstration environment

Pakistan Information Security Framework ISO/IEC 27001:2022 NIST CSF 2.0 NIST SP 800-53 CIS Controls 8.1 PCI DSS 4.0 NIS2 NCSC CAF SOC 2
Why we built it

Pakistan has the frameworks. It does not yet have one trusted map between them.

A bank or an operator now answers to PISF, to its sector regulator and to the international standards its partners ask for. Most of the underlying controls are the same. Proving that is still done again for every framework, by every organisation, on its own.

01

Every crosswalk is private

Each organisation builds its own mapping between frameworks in a spreadsheet, and nobody outside it can check the reasoning behind a single line.

02

Two auditors, two answers

The same PISF control can be mapped to ISO 27001 differently by two capable people, and there is no shared reference to settle which of them is right.

03

Change goes unnoticed

When a framework is revised, nobody knows which mappings moved, so last year's crosswalk quietly stops being true while everyone keeps relying on it.

How it works

Six steps from a framework document to coverage you can defend.

The order matters. Nothing reaches a coverage figure until it has an identity, a source and a person who approved it.

01 · Load

Any framework

National, international, sector or one you wrote yourself.

02 · Register

One identity

Each standard and version exists once, so everyone maps to the same thing.

03 · Import

Official crosswalks

Where a publisher ships its own mapping, it comes in exactly as published.

04 · Propose

AI fills the gaps

It proposes the relationships nobody has published yet.

05 · Approve

A person decides

Approve, approve as partial or reject. Pending counts for nothing.

06 · Use

Coverage and gaps

Built only from approved relationships, with the working shown.

Inside the product

A registry you can search, and a method you can check.

The directory is where a programme lead starts. The method is what an auditor asks about. Both are open to the people who have to rely on them.

Control directory

Every control, with what it is for.

The directory holds the reference text of each control with its area, criticality, risk level and business impact, next to how many approved relationships it already carries. The filters answer the first questions a programme lead asks, such as which critical controls are still unmapped.

  • Search across every field of every control
  • Criticality, risk and business impact on each one
  • Mapping governance totals at a glance
  • New frameworks loaded in place
ControlGraph · Control directoryDemo environment
The ControlGraph control directory for the Pakistan Information Security Framework, with the control library, framework registry and mapping governance totals above a filterable list of controls
Real product screen, sample dataAzbersInnovations
Coverage method

Every figure comes with its working.

Relationships use the relation types NIST published for exactly this job. Only approved, direct relationships count toward coverage, and every result names the version of the method that produced it, so the same figure can be reproduced a year later.

  • Approved relationships only, never pending ones
  • Each result carries an explanation
  • The method is versioned and published
  • Source scores are never created or changed
ControlGraph · Coverage method
RelationWhat it meansToward coverage
equalThe same requirement in different wordsCounts in full
supersetThe source fully contains the targetCounts in full
subsetThe target asks for more than the sourceCounts in part
intersectsThe two overlap without either containing the otherCounts in part
relatedUseful context, not a matchDoes not count
Coverage is an estimate, not an audit opinionAzbersInnovations
What else it answers

The questions people bring to a crosswalk.

A map is only worth building if it answers something on a working day. These are the questions we built it around.

Trace

Where does this control reach?

Pick any control and follow it through every framework it touches, with each link marked as official or as an approved AI proposal.

Test

Does our policy cover it?

Upload a policy once and see which controls it covers, partly covers or misses, framework by framework.

Prioritise

Where do we start?

See which controls carry across the most frameworks, so one piece of work covers the most ground.

Change

What moved this month?

When a framework is revised, the mappings it affects are flagged for everyone who relies on them.

AI in ControlGraph

AI proposes. People decide.

Reading two frameworks side by side and finding where they meet is slow work, and a machine does a good first pass at it. It is also exactly the kind of judgement nobody should take on trust, so the rules below hold whichever AI provider is in use.

01 · Propose

A candidate link

AI suggests how a control relates to one in another framework.

02 · Pending

It counts for nothing

Until someone approves it, it changes nobody's coverage.

03 · Approve

The right people decide

Shared mappings by the national operator. An organisation's own need two approvers in two roles.

04 · Protect

Approval sticks

Running the AI again never overwrites an approved relationship.

There is no open chat box. Every AI feature is a fixed task whose output is checked before anyone sees it.

Official crosswalks always take precedence over anything the AI proposes.

Models can be hosted inside Pakistan, so control text and policies never need to leave the country.

Why one national map

A map is only useful if everyone uses the same one.

NIST runs a national programme for exactly this, publishing reviewed mappings to its own frameworks. We think Pakistan should own the equivalent for PISF, and decide for itself how its framework relates to the rest of the world.

WhoWhat changes for them
The national operatorOwnership of the official PISF crosswalk, the method behind it and every approval
Sector regulatorsA clear view of where their rules already overlap PISF, so duplicate requests can be retired
Ministries and public bodiesPolicies tested against PISF, and one piece of work recognised several times
Banks and operatorsPISF, their sector rules, ISO 27001 and PCI DSS connected in one place
AuditorsA shared reference with the source and the approver of every mapping
Works with CyberNexus

Assessed once for PISF, estimated everywhere else.

CyberNexus keeps the assessment, the evidence and the Authority's verification. ControlGraph keeps the frameworks, the relationships and the coverage calculation. When an organisation finalises a PISF cycle, the results can travel across signed, and ControlGraph uses the Authority's verified score wherever one exists. Anything tampered with or replayed on the way is refused.

Questions we get asked

Before you get in touch

The questions that come up most often, answered the way we would answer them on a call.

How is this different from a mapping spreadsheet?

A spreadsheet records that someone believed two controls match. ControlGraph records the relation type, where it came from, who approved it and when, and it recalculates coverage from approved relationships only. You can check the reasoning behind any number it shows.

Does the AI map our controls automatically?

It proposes, and a person approves. A proposal changes nobody's coverage until it is approved, an organisation's own mappings need two approvers in two roles, and running the AI again never overwrites an approved relationship.

Is PISF already mapped to ISO 27001?

Not officially. No published PISF crosswalk exists yet, and building one properly needs the national operator to review and approve it. ControlGraph is built to hold that work and publish its method.

Does a coverage figure mean we are compliant?

No. It estimates how far work done for one framework carries toward another. It is not an audit opinion or a certification, and the platform says so next to every figure.

Which frameworks can it hold?

Any. National, international and sector frameworks load the same way, and an organisation can add its own private framework. The demonstration catalogue already holds PISF, ISO 27001, NIST CSF, NIST SP 800-53, CIS Controls, PCI DSS and others.

What about the licensing of standard texts?

Full standard texts are loaded only under the publisher's licence terms. Where a licence does not allow it, the control identifiers and relationships can still be held.

Bring the frameworks you answer to.

We will show you your own obligations in ControlGraph, with the relationships between them and where the gaps are. The demonstration runs on the real software, on your premises if you prefer.