Maps defined security controls and obligations across frameworks — ISO 27001, SOC 2, RBI, DPDP — to a single assessment workflow.
Control & compliance evidence intelligence
What you claim to control, proven the way an auditor would demand it.
NORMA™ — Normative Obligation, Risk & Mapping Assessment — is the evidence-assurance engine behind RixControl™, turning your security controls and compliance obligations into evidence-backed assurance across the CNIS™ platform before it ever reaches a dashboard.
Tap to pulse
ISO 27001Mapped
SOC 2Mapped
RBI IT FrameworkMapped
SEBI CSCRFMapped
DPDP ActEvidence pending
CERT-In GuidelinesMapped
NIST CSFMapped
PCI DSSGap flagged
ENGINE NORMA™
PLATFORM CNIS™
STATUS MAPPING
Mapped
Evidence pending
Gap flagged
142Controls mapped
Evidence sources linked
3Gaps flagged this cycle
0–100CRI scale, evidence-weighted
Not a checklist
Assessment that runs, not a spreadsheet that decorates
Control mapping builds an initial picture about what's actually covered — pulled from policy documents and evidence gathered across the CNIS™ platform. Evidence correlation, run by the NORMA™ engine, confirms or rejects sufficiency, scoped to the framework in question.
Every control that survives assessment gets a source and its supporting context — never a bare pass/fail with nothing behind it.
CNIS™ architecture
NORMA™ speaks the same language as the rest of CNIS™
Every module — NORMA™ included — moves evidence through the same three-stage framework before it reaches a decision-maker.
S
Signals
Deviations across your control landscape — new obligations, expired evidence, unresolved exceptions.
→S
Scenarios
Signals resolved into the most significant control gap — not a flat checklist of unrelated exceptions.
→I
Intelligence
A structured CRI result your team — and the rest of CNIS™ — can act on directly.
// SIGNALS → SCENARIOS → INTELLIGENCE — the SSI framework CyberNeurix Pulse runs across cybersecurity and neurotechnology alike.
Product
Can we actually prove the controls we say we have?
Not another GRC platform. NORMA™ maps your defined controls and obligations to an assessment workflow, evaluates the evidence behind them, and hands your team a structured result instead of a compliance checklist.
Map
Evidence
Shows an evidence-oriented view of control assessment, not a generic pass/fail with no backing.
Gaps
Surfaces exceptions and areas lacking sufficient evidence across the assessment.
Feed CNIS™
Outputs a structured control-assessment result that flows into the wider CNIS™ decision context.
Why it matters
Control existence and control evidence are not the same thing
- Auditors and security leaders need to understand the evidentiary basis of a control assessment, not just that a control exists on paper.
- Organizations manage multiple obligations across frameworks and need a common assessment view.
- Evidence often lives scattered across the platform and sits disconnected from the compliance record it should be informing.
- Security-control evidence as the primary product object, not a checkbox.
- Explicit separation between what is known and what lacks sufficient evidence.
- Useful to security and GRC stakeholders without becoming a full enterprise GRC replacement.
- Designed to contribute a control view to the wider CNIS™ picture.
Measurement & output
CRI — an honest band, not false precision
This page describes what the band means and how teams read it. What sits behind it — the obligation mapping, evidence-class weighting, and calibration — is deliberately not published.
Illustrative readout
Control Relevance Index
Insufficient evidenceFully evidenced
Shape only — no real scoring, thresholds, or calibration data shown.
A band reported honestly, with its supporting context available for review.
A clear separation between what NORMA™ can evidence and what your team signs off. Structured for an auditor, a reviewer, and the next engine in the chain.
Competitive landscape
Where NORMA™ sits, and what it defends
A capability-level view based on public 2026 market sources. Not a claim of feature parity with every platform listed — a statement of category boundary.
| Market alternative | Category | Typical strength | CNIS™ distinction |
|---|---|---|---|
| ServiceNow IRM / GRC | Enterprise GRC / IRM | Broad enterprise governance, risk and compliance workflows. | NORMA™ is positioned around evidence-backed security control assessment rather than attempting to replace a broad enterprise GRC system. |
| RSA Archer | Enterprise GRC | Enterprise risk, compliance and governance management. | NORMA™ is more focused on the evidentiary condition of security controls and obligations. |
| MetricStream | GRC / compliance | Large-scale governance, risk and compliance management. | NORMA™ emphasizes assessment evidence and security-control context rather than broad enterprise workflow coverage. |
| Vanta / Drata | Compliance automation | Automated evidence collection and audit-readiness workflows. | NORMA™'s product boundary is security-control assessment — not marketed as a universal audit automation platform. |
Market landscape reviewed: CIOPages GRC buyer guide (June 2026); ComplianceStack 2026 compliance software comparison.
Differentiation strategy
Assure the evidence. Don't become the GRC system of record.
GRC platforms are good at holding policy and bad at proving it. NORMA™ does not try to replace the register — it records the basis for each claim in it, so how a control was established stops being invisible.
Where NORMA™ competes
- Security-control evidence as the primary product object, not a checkbox.
- Explicit separation between what is known and what lacks sufficient evidence.
- Useful to security and GRC stakeholders without becoming a full enterprise GRC replacement.
- Designed to contribute a control view to the wider CNIS™ picture.
Where it deliberately doesn't
Do not position this product as a universal replacement for SIEM, enterprise GRC, global threat intelligence, vulnerability management, or broad enterprise risk software.
The strategy is specialization plus composition. NORMA™ answers whether a control can be proven; VERITA™ answers whether it is still running. Neither pretends to be the other.
CNIS™ architecture position
Where NORMA™ sits in the pipeline
Input
Evidence & sources
Approved, product-specific evidence across the CNIS™ platform
→
RixControl™
NORMA™
Domain analysis → CRI
→
Output
CNIS™
Structured intelligence for wider security context
Use cases
What assurance teams actually do with it
Baseline
Establish an evidence-based baseline for control & obligation assessment.
Investigate
Pull the evidence trail behind a specific obligation before the auditor asks for it.
Report
Present control assurance with its verification basis visible, rather than a single reassuring percentage.
Connect
Give VERITA™ the control set to watch, and give INFERA™ the assurance picture to reason over.
Buyer profile
Bought after the first audit finding nobody saw coming
The buyer has a control register that says everything is fine and an auditor who disagreed. What they need is to know which of their green controls are green because someone typed it, and which are green because a system confirmed it.
Can RixControl™ give us a clearer view of our control & obligation assessment position?
Can we see which controls are system-established and which are only attested?
Will a control with thin evidence ever present as more assured than it is?
Can we scope this to one framework or business unit before expanding?
Know what you can prove, not just what you claim
A live demonstration walks through a realistic input, the RixControl™ workflow, the resulting CRI, supporting evidence, and the decision it supports.