UniSentinel module

Map your controls once, comply with every framework

Bring regulations, standards, contracts and your own internal mandates into one requirement library, map them to a single company control set and policy registry, and close what's left as tracked gaps — with statement-of-applicability and gap reports ready whenever someone asks for proof.

Importable requirement librariesCommon-controls mappingApproval-gated policiesSoA & gap reports

Capabilities

One place for every obligation you answer to

Built for compliance teams who juggle multiple frameworks — and refuse to maintain the same control in five spreadsheets.

Every requirement source, one library

Track requirements from regulations, standards, contracts and fully custom internal mandates side by side — organized hierarchically, the way frameworks are actually written.

Importable requirement libraries

Public-domain frameworks like NIST import ready to use. Licensed standards such as ISO 27001 and SOC 2 are tracked as requirement codes with paraphrases — honest handling that respects the licenses you hold.

A policy registry that governs itself

Register every policy with its metadata and document, keep full version history, assign owners and review cycles, and publish only through an approval gate.

Map once, comply many

One company control set, mapped across frameworks: a single control or policy satisfies many requirements from many sources at once, so each new framework starts mostly covered.

Gaps that end in action

Unmet requirements become tracked gaps with actions attached — a working list of what's missing, who owns it, and how it gets closed.

Proof on demand

Statement-of-applicability and gap-analysis reports, plus compliance-posture widgets for your dashboards — coverage you can show, not just claim.

Standalone by design

Complete on day one — no other module required

License Compliance alone and you still run the full loop: libraries, policies, mapping and gaps. Every integration has a built-in local fallback.

  • Build requirement libraries and the control mapping matrix with nothing else installed.
  • Run the policy registry — versions, owners, review cycles, approvals — entirely on its own.
  • Track gaps with lightweight built-in action items.
  • When you license a counterpart module later, a guided wizard promotes your local data — nothing is retyped, nothing is lost.
RequirementsControl mapping
Access control policy in placeISO A.5.15Mapped
Logical access restrictedSOC 2 CC6.1Mapped
Identities & credentials managedNIST PR.AC-1Mapped
Customer data retention termsCTR-012Partial
Quarterly access reviewINT-004Gap

How it works

From obligations to proof of coverage

  1. 01

    Import

    Load requirement libraries or define custom sources — regulations, standards, contracts and internal mandates, structured hierarchically.

  2. 02

    Map

    Map your single control set and policies to requirements — one mapping can satisfy many frameworks at once.

  3. 03

    Close

    Turn unmet requirements into gaps with owned actions, and publish policies through approval-gated review cycles.

  4. 04

    Prove

    Run statement-of-applicability and gap-analysis reports, and watch posture widgets track coverage over time.

Frequently asked questions

Do you include the full text of standards like ISO 27001?

Only where licensing allows. Public-domain frameworks such as NIST import in full. Licensed standards like ISO 27001 and SOC 2 are tracked as requirement codes with paraphrases — you work against your own licensed copy of the text, and we never reproduce it.

Can we track contracts and internal requirements, not just standards?

Yes. Requirement sources cover regulations, standards, contracts and fully custom internal mandates, and requirements are hierarchical — so a contract's obligations or your own internal baseline sit alongside imported frameworks and map to the same control set.

How does one control satisfy several frameworks?

Through common-controls mapping. You maintain a single company control set, and each control or policy maps to any number of requirements across sources. Adopt a new framework and the matrix shows immediately what's already covered and what's a genuine gap.

How is policy publication controlled?

Every policy has an owner, a review cycle and full version history, and publication is approval-gated — a new version goes live only after the defined approvers sign off, with the decision recorded in the audit trail.

Get started

See UniSentinel running on your terms

Book a 30-minute walkthrough. We'll map your program to the modules you need — cloud, on-prem Linux or Windows Server.

Every module works standalone. License only what you need — grow when you're ready.