Qatar NIA Policy 2.0

From first analysis to audit day.

We built ComplianceVault for teams working through Qatar's National Information Assurance Policy. It starts where the policy starts, with the business processes that matter and the information they depend on, and uses that to decide how many controls you actually owe before a single one is assessed.

ComplianceVault · Control assessmentDemo environment
The ComplianceVault control assessment list, filterable by domain, section, baseline, type, objective and status, with each control marked fully applied, low applied or not evaluated
Real product screen, sample dataAzbersInnovations

Screens from a ComplianceVault instance loaded with a sample agency. The processes, assets and results are sample data.

356NIA Policy 2.0 controls in the catalogue, with their mappings to ISO 27001, PCI DSS and NIST
5impact dimensions weighed in every business impact analysis
3security levels, each setting how many controls a domain owes
4assessment outcomes, each earning its own share of credit
Why it exists

The policy asks for order before it asks for controls.

Most teams begin at the control list, which is the wrong end. Until you know which processes cannot stop and which information needs the most protection, choosing controls is guesswork with a template attached. ComplianceVault holds the order the policy expects.

01 · Processes

Impact analysis

Score each process on reputation, external, internal, legal and economic impact.

02 · Assets

Classify information

Rate each asset for confidentiality, integrity and availability.

03 · Level

Set the target

The highest rating sets the security level, and the level sets the controls owed.

04 · Assess

Answer each control

Fully, partially, lightly or not applied, with the reasoning kept.

05 · Evidence

Attach the proof

Files stay with the control they justify, not in a shared folder.

06 · Track

Stay audit ready

Every change is logged, so the history explains the current state.

Security level

Your analysis decides how much you owe.

An agency whose information is all low impact owes the baseline controls. One with a single high impact asset owes the baseline plus two more controls in every domain. ComplianceVault works that out from the ratings you give your assets and moves the target the moment a rating changes, so nobody discovers at audit that the goalposts were in the wrong place.

  • Impact weights you can adjust to your organisation
  • Criticality score calculated for every process
  • Security level recalculated whenever an asset changes
  • The resulting control target shown on the dashboard
ComplianceVault · Business impactDemo environment
Business impact analysis in ComplianceVault with an aggregate security level and six scored business processes
Real product screen, sample dataAzbersInnovations
Domains

Every domain, measured against its own target.

Each domain shows baseline and additional controls separately, so a strong result on the easy half cannot hide a gap in the half the security level added. The weakest domain is obvious at a glance, which is where the next month of work should go.

  • Baseline and additional progress shown separately
  • Credit that reflects partial and light application
  • A published scoring method anyone can check
  • Roles for administrators, auditors, commenters and viewers
ComplianceVault · DomainsDemo environment
ComplianceVault domain cards showing compliance percentages and baseline and additional control progress
Real product screen, sample dataAzbersInnovations
Where it sits

Deliberately specific.

ComplianceVault knows one policy well rather than many loosely, which is what a team in the middle of a NIA programme needs from it. It came out of our own delivery work and we still use it on engagements.

Where an organisation answers to more than one framework, the mapping problem is the one ControlGraph is built for. For Pakistan's national framework, CyberNexus carries assessment through to certification.

Assessment records

Every control answer keeps its assessor, its date and the material behind it.

Cross references

Each NIA control shows where it meets ISO 27001, PCI DSS and NIST SP 800-53.

Change log

Every edit is recorded with who made it and when.

Audit pack

The submission comes from the same records the team worked in all year.

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.

Is this only for Qatar's NIA Policy?

Yes, deliberately. It holds the NIA Policy 2.0 controls with their cross references and follows the order the policy expects. Organisations answering to several frameworks at once are usually a better fit for ControlGraph.

Where does it fit against CyberNexus?

They serve different frameworks. ComplianceVault carries a Qatar NIA programme from impact analysis to audit day. CyberNexus is built for Pakistan's framework, with an Authority portal for national review and certification.

Can we start part way through a programme?

Most people do. Tell us which stage is currently stuck, because that is usually a more useful starting point than the beginning.

What happens to our evidence?

It stays linked to the control it justifies rather than sitting in a folder near it, and it stays under the same isolation and access rules as everything else we build.

Working through a NIA programme?

Tell us where you are in it. The useful conversation usually starts with whichever stage is currently stuck, and we can show you that stage in the product.