Skip to main content
Security Posture shows you what is wrong; this is how you act on it. The actions live in two places, and it’s worth knowing which is which.

​
Where the actions are

On the dashboard

In Priorities · fix first, each finding carries a Remediate button beside its risk score — the fastest path from “this is the worst thing” to “fix it”.

On a target

Open a device or integration and go to its Findings tab. Each row has a menu with Send to chat and Silence — and on a finding that is already silenced, Reactivate takes the place of Silence.
A target’s Findings tab splits into three views — Priorities · fix first, Re-categorized, and All findings — and you can search by check, resource or region and filter by severity, status and category.
The actions available on a single finding

​
Remediate

Remediate hands the finding and its affected target to chat, where the right specialist does the work:

On a host — Perseus

Perseus applies the fix on the device through the Myrmex agent.

On an integration — Hydra

Hydra applies the fix on the connected tool.
As with every operational action, the agent proposes the fix and carries it out in front of you, so you stay in control of what actually runs.

​
Send to chat

Send to chat drops the finding into the conversation without committing to a fix. Use it when you want to understand the finding first — what it is, why it matters, what it touches — and decide afterwards.

​
Silence a finding

Not every finding gets fixed. When you choose to live with one, Silence it. What the panel asks of you depends on what Athena thinks of the finding, and the difference matters.

A finding Athena hasn't called a real risk

The Silence finding panel asks for a justification and, optionally, a validity date of your choosing. Cancel or Silence, and that’s it.

A finding Athena has confirmed as real

The panel opens with its verdict and requires a signed risk-acceptance letter before the finding goes quiet. The steps below describe this path.

​
When Athena has confirmed the risk

1

Athena tells you whether it's noise

The panel opens with a verdict in the heading — “This is NOT noise” — and a confidence percentage behind it, followed by the technical reasoning. When the platform has already validated a finding as real, it says so before you silence it.
2

It tells you what to consider first

A Before silencing, consider list spells out the remediations available to you — the concrete alternatives to accepting the risk.
3

You justify it and name the signers

A justification is required, alongside the responsible signer and their email, both pre-filled with your account. On a critical finding the form grows: Second approver and Approver email become required too, so no one accepts a critical risk alone.
4

You preview the letter

Preview Letter renders the Risk Acceptance Letter in full — the finding, the target, the verdict, the justification — and Send issues it.
5

The signers sign it

The letter is created pending signature and the signers are notified. Signing happens on its own page, Myrmex Sign, which verifies the signer’s identity before recording the signature.
The finding is not silenced when you submit the form. It is silenced automatically once all signatures are collected — so a critical finding stays in your queue until both the responsible signer and the second approver have signed.
This is the “AI proposes, you approve” pattern inverted: here the human proposes to accept a risk, and the AI is the one pushing back with evidence before it lets the finding go quiet.
Once silenced, the finding drops out of your active priority queue and stops weighing on your score.

​
An acceptance expires — the finding comes back

A risk acceptance is not permanent, and you don’t have to remember to revisit it. The letter states its own term:
This acceptance is valid for 90 days. On expiry it lapses automatically: the finding returns to the active state in your security posture and has to be re-assessed — either remediated, or accepted again under a new letter.
The letter is also explicit about what accepting a risk does not do: it doesn’t fix the vulnerability, and it doesn’t transfer responsibility for any impact. You can also end an acceptance early. On a silenced finding, the row menu offers Reactivate where it offered Silence — the finding returns to your posture immediately, and the letter stays on file as the record of the period it covered. In the lighter flow, where no letter is involved, the validity date is yours to set when you silence.

​
Where the letters live

Every risk-acceptance letter is an artifact. Find them under Artifacts → Risk Letters in the Directory, where a coloured dot tells you whether a letter is still pending signature or already signed. Open one to read it, or Export PDF to share it. The document — the Risk Acceptance Letter — carries its own number, issue date, organisation and tenant, and is structured for an auditor:
Signatures are collected through Myrmex Sign, with OTP authentication, a read receipt, a timestamp and a SHA-256 / PAdES integrity seal. The audit trail and the authenticity check travel with the final document.
The silence panel, with the justification, the responsible signer, the second approver and the Preview Letter button

​
When Athena disagrees with the scanner

Silencing is the decision you make by hand. Athena also makes one on its own: findings whose severity doesn’t survive contact with your environment are re-scored, and they collect in the Re-categorized view — downgraded when the platform proves they’re noise, elevated when real exposure makes them worse than the scanner said. See Smart re-categorization.

​
Where to go next

Security Posture

Back to the scored dashboard and the controls table.

Frameworks & scanning

How findings are produced and mapped to frameworks.