Policies Page
This page covers Policies in the hosted dashboard’s sidebar, part of the Hosted plan and above. Every time you tell Omnodex what to do about a kind of finding (let it through, mute it, change how serious it is, or on Pro stop it), that decision becomes a policy entry. The Policies page lists them all, for your whole account, and lets you change or remove them.
Without it, a decision lives on one machine. With it, you make the call once and every machine on the account picks it up, along with this dashboard.
When to use it
Section titled “When to use it”- A rule keeps flagging something you’ve already checked. A test fixture with a fake key, an internal host your agents are meant to reach. Allow or mute it for that path, host or project, and the noise stops everywhere.
- Something matters more to you than the rule’s default. Raise its severity, so it scores higher and stands out in the dashboard and in notifications.
- You want certain calls stopped or held for you. On Pro, with guardrails on, block or hold calls like one you’ve seen.
- You want to review what’s been switched off. The page is the single list of everything allowed, muted or downgraded, and who added it when.
Adding an entry
Section titled “Adding an entry”You add entries from a finding, not from a blank form, so each one starts from something your agents really did.
-
Open a finding. On the Dashboard or the Investigations page, select a risk finding to open its details.
-
Choose an action. Under Actions: Allow like this, Mute, Change severity, or on Pro Block like this and Hold like this.
-
Choose what it covers. Every finding from that rule, or only this path, host, command or tool; and everywhere, or only in this project.
-
Check the preview. Before you save, the dashboard shows how many findings from the last 30 days the entry matches. A surprisingly large number usually means the scope is wider than you meant.
-
Save. This dashboard changes at once, past findings included. Machines pick the entry up within about 15 minutes, at their next background sync.
You can also start an entry from the local dashboard on a machine. It opens Policies with the entry filled in and a note that a link proposed it. Nothing is added until you press Add, and an entry that allows, mutes or lowers a severity says what it would turn off across the account. Add one only if you started it yourself: anyone can make a link like that.
Reading the list
Section titled “Reading the list”Entries are grouped by the rule they apply to, or by category or severity for broader entries.
| Column | What it shows |
|---|---|
| Scope | What the entry is narrowed to (a path, host, command prefix, tool or credential fingerprint), and the project, or everywhere |
| Effect | What it does: allow, hold or block, mute or do not mute, and a new severity. A changed severity shows the rule’s own as recommended beside it |
| Added | The date, and who added it |
Show muted findings puts muted findings back into the rest of the dashboard without changing any entry. It’s a quick way to check what a mute is hiding, and this browser remembers the setting.
Changing or removing an entry
Section titled “Changing or removing an entry”Select Edit on a row to change its scope value, its project (leave it blank for everywhere), its verdict, whether it mutes, and its severity. Save applies it the same way as a new entry. Remove deletes it; machines stop applying it at their next sync.
Without guardrails, an entry can keep a block or hold it already has, but you can’t choose a new one.
How it fits with the CLI
Section titled “How it fits with the CLI”| Where an entry lives | Applies to | Set with |
|---|---|---|
| The account (this page) | Every machine on the account, and the hosted dashboard | Finding actions here, or a link from the local dashboard |
| One machine | That machine only | omnodex policy on the machine |
When both have an entry for the same thing, the machine’s own entry wins, so a team can share one account policy while one machine keeps a local exception. The full rules are in Which entry wins. A machine stops pulling the account policy with OMNODEX_POLICY_PULL=0.
Entries are encrypted before they leave your browser, with one copy for each data stream, so Omnodex stores them without being able to read them. A stream connected after your last save gets its copy the next time you open the dashboard.
Next steps
Section titled “Next steps”- Shadow Mode and Guardrails: what block and hold do on each agent
- Hosted Dashboard: finding actions in context
- Risk Library: what each rule looks for, and its false positives