Current Doc

Exceptions

Use Browse Docs to switch sections and search the full docs list.

Documentation

Blue Lantern Security Docs

Learn how to use the marketplace, run security tools, and integrate via the API.

Exceptions

Tell Blue Lantern when a failed check is covered by a control you already have, so it stops counting against you while staying on the record.

Sometimes a posture check fails for a control your organization actually has. The most common case is an EDR or antivirus product that our device checks don't recognize: every device reports the EDR check as failed, every device run shows At Risk, and alert rules keep firing. An exception records that a compensating control covers the check. The check keeps running, but it shows as Covered by exception instead of failing and no longer counts toward verdicts, failed-check totals or alerts.

An exception is a statement your organization makes, not something Blue Lantern verifies. Every exception records who made it, when, and why, and it stays visible wherever the check appears.

What can be excepted

Any failed posture check can be excepted, including critical ones:

  • Device checks from the macOS and Windows agents, and the device health checks from the CrowdStrike Falcon and Microsoft Defender integrations.
  • Identity checks: MFA registration, dormant accounts, and organization-wide MFA enforcement.
  • Mail posture checks: DMARC, SPF and DKIM, auto-forwarding, forwarding addresses, and suspicious inbox rules.
  • AI exposure checks on third-party apps.
  • Cisco Meraki and Umbrella configuration checks.

Checks we couldn't observe can be excepted too. A device check shown as Incomplete couldn't run on that device, for example because the agent hasn't been granted Full Disk Access. Nothing failed, but the device stays At Risk because we can't see the control, and the report's verdict says so. Fix what stopped the check from running, or, if the control is covered another way, except it like a failed check.

Phishing, malware and URL verdicts can never be excepted. They aren't controls: a compensating control doesn't make a malicious attachment safe.

Add an exception

You need to be an admin of the account.

  1. Open the report with the failed check from the Monitoring Hub, such as a device, identity or mail posture report.
  2. Click the failed check to open it, then click Except this check.
  3. Choose what it applies to:
    • This device, user, domain or app only, prefilled from the check.
    • Entire organization: every user, device and integration on the account, including ones added later.
  4. Enter a reason of at least 20 characters explaining how the control is covered, for example "Huntress EDR is deployed to every laptop through our RMM". Optionally name the compensating control and set an expiry date.
  5. Read and tick the attestation, then click Create exception.

The report you were on is re-scored straight away, and the check shows as Covered by exception. Earlier reports keep the scoring they had: a report from last week still shows what was true last week.

How the scope works

  • One exception covers a control on every platform. Some controls are checked differently on each platform. An exception for endpoint detection and response covers the macOS and Windows agent checks and the Falcon and Defender health checks together, and the same applies to disk encryption, firewall, automatic updates, screen lock, backup, password manager and MDM. The dialog tells you when this applies.
  • Inbox rules and forwarding addresses are excepted one at a time. An exception covers that specific rule or address on that mailbox, never the whole mailbox or the whole organization. A new rule that appears later is a new finding.
  • An organization-wide exception and a per-asset exception can exist for the same control.

What changes when a check is excepted

  • The check shows a shield icon and Covered by exception, never a plain Pass. Hover over it to see the reason, or open it to see the scope, reason, compensating control, who declared it and when, and what the check originally found. Reports gain a Covered filter.
  • The run's verdict and failed-check count are recalculated without the excepted check, so the Monitoring Hub, alert rules and the integration summaries all agree. Alert rules stop matching on checks that are now covered.
  • The check still runs on every scan. If you remove the exception, or it expires, the next scan reports the real result.
  • Members see excepted checks as Covered by your organization, so someone looking at their own device report knows why a check isn't failing.
  • CSV exports mark excepted checks as Covered by exception.

The attestation

To create an exception you confirm:

I confirm that a compensating control is in place for this check and that Blue Lantern Security has not verified it. I accept responsibility for the accuracy of this statement on behalf of my organisation.

We store which version of this statement you accepted, alongside your name, the time, and your reason.

Manage exceptions

The Exceptions page in the left navigation lists every exception on the account with its control, scope, reason, who declared it and when, its expiry, and a status:

  • Active: the exception is applied when its check fails.
  • Expired: its expiry date has passed, so the check fails again from the next scan.

Exceptions can't be edited, because each one is a signed statement. To change the reason or scope, remove the exception and create a new one.

To remove one, click Remove and confirm. The check fails again wherever it still fails, and the latest report for each affected asset is re-scored straight away. Removed exceptions stay on the page under Removed exceptions, with who removed them and when, so the full history of what your organization claimed is kept.

Members can view the Exceptions page but only admins can add or remove exceptions.

Need Help?

Can't find what you're looking for? Reach out and we'll get back to you.

Contact Support