Security

Compliance Policy

Define your own compliance rules on top of built-in standards. Enforce them continuously across your entire fleet. Every device, every change, every time.

NIS2ISO 27001PCI-DSSCISNIST CSFHIPAA
  • ✓Built-in NIS2 / ISO 27001 / PCI-DSS / CIS templates
  • ✓Custom rule builder (no scripting)
  • ✓AND/OR conditional logic
  • ✓Applies to switches, routers, firewalls, APs
  • ✓Continuous re-evaluation on config change
  • ✓Weighted scoring per rule

Standards + Your Own Rules

Start from industry frameworks and extend them with rules specific to your infrastructure, your team, and your regulatory context.

📋

Built-In Standards

Start from NIS2, ISO 27001, PCI-DSS, and CIS templates. Pre-built rule sets ready to activate in one click.

🔧

Custom Rule Builder

Write your own rules using plain readable conditions. No scripting, no regex, no YAML. Just logic.

⚡

AND/OR Logic

Rules can combine multiple conditions. SSH v2 AND banner set AND Telnet disabled, all in one rule.

🔌

All Device Types

Switches, routers, firewalls, and access points. Every device class evaluated against the same rule engine.

🔄

Continuous Enforcement

Rules are re-evaluated on every config change. No waiting for the next scheduled scan.

⚖️

Weighted Scoring

Each rule has a configurable weight (0–10) affecting the overall compliance score. Your priorities drive the number.

How the Rule Model Works

A rule is a set of plain-language conditions combined with AND/OR logic. No scripting. No configuration language to learn. Just readable statements that match what you actually want to enforce.

  • 1

    Plain readable conditions

    "Is SSH v2 enabled AND is Telnet disabled AND is banner login set", each condition is a statement anyone on your team can read.

  • 2

    Group by standard or category

    Rules can be grouped by framework (NIS2, ISO 27001) or by your own categories (access hardening, logging, encryption).

  • 3

    Weighted scoring per rule

    Each rule carries a configurable weight from 0 to 10. A rule with zero weight doesn't affect the score. Maximum weight drives it. Your priorities, not ours.

RULE: SSH Hardening
Condition: SSH v2 enabled
AND: Telnet disabled
AND: Banner login set
Weight: 8 / 10, Standards: NIS2, ISO 27001

Rule: SSH Hardening

Weight: 8/10
SSH v2 enabled✓ Pass
Telnet disabled✓ Pass
Banner login set✗ Fail
SNMP v3 only✓ Pass
NTP server configured✓ Pass
Password complexity policy✗ Fail

Compliance Score

67/ 100

4 of 6 conditions passing · 2 violations affecting score

FAQ

Frequently Asked Questions

Common questions about the compliance policy engine

Which compliance frameworks are included out of the box?

ConnectMyAssets ships with built-in rule templates for NIS2 Article 21, ISO 27001 Annex A, PCI-DSS, CIS Benchmarks, NIST CSF, and HIPAA. Each template is a curated set of rules mapped to the specific controls of that framework, ready to activate against your device inventory with one click.

Can I write custom compliance rules without scripting?

Yes. The rule builder uses plain readable conditions, no scripting, no regex, no YAML. You combine conditions using AND/OR logic in the interface. For example: SSH v2 enabled AND Telnet disabled AND banner login set. Any engineer on your team can read, write, and modify rules without specialist knowledge.

How does weighted scoring work per rule?

Each rule has a configurable weight from 0 to 10. A rule with weight 10 has maximum impact on the overall compliance score; a rule with weight 0 is evaluated and reported but does not affect the score. This lets you reflect your organisation's actual risk priorities rather than treating all controls equally.

Are rules re-evaluated automatically when a configuration changes?

Yes. Rules are re-evaluated in real time every time a configuration backup is collected. There is no need to trigger a manual scan. If a device falls out of compliance after a change, the score updates immediately and an alert can be sent to your team.

Can I apply different policies to different device types?

Yes. Policies can be scoped to specific device groups, vendors, or device types. For example, you can apply a stricter firewall hardening policy to perimeter devices while using a lighter policy for access layer switches. Rules that are not applicable to a device type are simply excluded from that device's evaluation.

Can compliance rule results be exported for an audit?

Yes. You can export a full compliance evidence pack as a PDF. It includes per-device rule outcomes, pass/fail status, timestamps of evaluation, rule descriptions, and framework references. The export is designed to be handed directly to an auditor or regulatory body without further formatting.

Build Your Compliance Baseline

Standards + your own rules. Continuous. Automatic.