Rules and Compliance
Findings are security and compliance issues detected against your graph. Each finding is the result of a rule (a Cypher query) matching one or more nodes in the inventory that Cartography syncs into Neo4j (cloud accounts, identity, code, devices, ontology). Rules re-run after every sync, so findings reflect the latest snapshot.
Rule status
- Has findings: the rule matched one or more resources.
- Pass: the rule ran and matched nothing.
- Disabled: the rule is turned off and is not evaluated.
- Error: the last run failed. Hover the badge, or open the rule, to see what went wrong, how to fix it, and when the rule last ran cleanly. Until it runs cleanly again, its findings are not fully refreshed.
Working with a rule
Each rule on the Rules page exposes its title, description, tags, first seen, and last match. Click the rule to expand three tabs:
- Results: currently matching resources.
- Accepted: results you have acknowledged as acceptable risk.
- History: resolved results, retained for 48 hours.
Each row shows the resource name, source provider, first and last seen, and the rule-specific output fields. Use the View in Neo4j Browser action on any row to open the underlying query around that resource.
Accept a result
- Expand the rule and select one or more rows in the Results tab.
- Click Accept.
- Pick Until a date or Permanent.
- Add a reason (required for audit trail).
- Confirm.
Accepted rows move to the Accepted tab. They count toward acceptance, not active findings, until the Until date passes, at which point they re-enter Results automatically.
To revert, open the Accepted tab, select the row(s), and click Unaccept.
Use date-bounded acceptance for known-temporary exceptions (a migration in flight, a vendor remediating). Use permanent acceptance for design decisions, and put the rationale in the reason; auditors read it.
Disable a rule
If a rule does not apply to your environment, click Deactivate on the rule row, choose Until a date or Permanent, and confirm. Disabled rules stay listed at the bottom of the Rules page but do not run.
Filter
The Rules page filters by status, tag, and framework. Filters compose; the URL updates so a filtered view is shareable.
Export
Click Export at the top of the Rules page to download every rule, every active result, and every acceptance as JSON. Use this for offline review or to feed an external GRC tool.
Compliance frameworks
A framework is a curated benchmark whose requirements are mapped to Subimage rules (CIS AWS, CIS GCP, CIS Azure, etc.). Open Compliance to manage them.
- Enable / disable a framework toggles every rule it owns. Rules disabled this way are restored if the framework is re-enabled.
- Compliance score = passing assets / total assets across the framework's rules. The score is snapshotted daily.
- History charts the score over time. Click any point to see the per-rule pass/fail breakdown for that day, useful to attribute a drop to a specific rule.
A rule that belongs to multiple frameworks contributes to each independently.
Notifications
Two notification triggers are tied to findings. Configure them in Settings → Notifications alongside the Slack, email, or webhook destination.
- First-time enabled: fires the first time a newly enabled rule produces findings. Use this when rolling out a new policy: the alert tells you the rule is detecting something instead of failing silently.
- Weekly summary: counts of new, resolved, and accepted findings over the past seven days, grouped by tag.
Custom rules
A custom rule is a detection you write in Cypher. It runs with the other rules and appears in the same list with a custom badge. What each setting does — the query, the affected asset, the identity fields, and the display field — is covered in Custom Rules.
Programmatic access
Every action above is also exposed via MCP, so an agent can list rules, fetch findings, and read framework scores. The relevant tools are subimageListRules, subimageGetRuleHistory, subimageListFrameworks, and subimageGetFrameworkHistory. Current findings are Signal nodes in the graph, read with subimageRunCypher via the signals-via-cypher skill. Use subimageListRules(view="custom_definitions") for tenant-authored Cypher definitions. See Connect via MCP.
Rules query Neo4j directly. If a rule starts erroring after a Cartography upgrade, the most likely cause is a renamed property or label. Open the rule to read the reason and fix hint, then select Edit and update the query.