Skip to main content
Preview. This part of the console is still being built. What you see here describes the intended behavior and can change before general availability.

Events and exceptions

A policy in audit has just told you that forty resources are non-compliant with it. Some of those are real work. Some are a known gap you agreed months ago. If the only way to quiet the second kind is to loosen the policy, the policy stops meaning anything. Events and exceptions keep the two apart.

An event is a decision, not a finding​

When a control of an Audit or Enforce policy fails on a resource, Dwaar opens an event. It stays open until the control passes again, then it is resolved. If it fails again later, it is reopened rather than created twice.

An event points at what failed: the findings the control counted, or the settings and facts it judged. It does not copy them as new findings, so your finding counts and grades do not change when you add or edit a policy.

Policies in Observe open no events and send no notifications. You only see which resources they find non-compliant, on the policy itself.

Where you see them​

  • Guard Center, then Events: every event in your organization scope, with filters for status, severity, resource type, policy and whether an exception covers it. Click a row to see why it fails, the linked findings, the policy and its mode, the revision that judged it and its dates. Above the list: compliant, non-compliant and not evaluated resources, then recent, open and overdue events.
  • A resource's Guard tab and a product's Guard tab: the compliance summary and the events of that resource or product.
  • A policy's Events tab: the events it has open. Its Overview shows its compliance.
  • Home: one compliance pane for your scope.

An event belongs to the resource's organization. A policy owned by a parent organization still opens its events in the child organization, so the people who own the resource see them.

A Fixes applied within the SLA event carries a due date: when the oldest finding it counts breaches its severity's limit.

Exceptions​

An exception exempts a resource, or every resource of a product, from one policy or from one of its controls, until a date you choose.

  1. Open the event and choose Request an exception. Give a reason and an end date at most 365 days away, then Send request. You can also create one from Guard Center, then Exceptions.
  2. The exception is Pending approval. Someone else with permission to approve exceptions opens the row menu on Exceptions and chooses Approve or Reject. You cannot approve or reject your own request.
  3. While the exception is Active, the event stays open but reads as excepted. The resource is not counted as non-compliant for it, and it sends no notifications.
  4. Dwaar sends a notification seven days before the end, and another when it ends. From then on the event counts again.

To keep an exception longer, extend it from the row menu. An extension is a new decision, so it needs an approver who is not you. An approver can also Revoke an exception at any time.

note

To accept the risk of one finding, accept it on the finding itself instead. An accepted finding stops counting in every control, which is narrower than an exception and is usually what you want.

Try this next​

Filter Events to open, critical ones and pick one you know is a deliberate gap. Request an exception for it with a real end date, and ask a colleague to approve it. Then watch the compliance rate move without loosening the policy.