Policy Center: Reviewing Open Incidents

Name: Policy Center: Reviewing Open Incidents
Uploaded: 2025-09-23T16:39:56.387Z
Duration: 4 min 17 s
Description: Automate incident resolution with Atlan's policy center, ensuring continuous data compliance and freeing your team from manual checks.

Join Live Demos Talk to Us

Transcript

4 min

00:00 — What open incidents are on the policy center
Automated incidents occur when any asset or multiple assets in scope do not comply to the rules defined. Now since we have set up a policy with additional rules, our next step is to check for any incidents that may have been created due to those rules and assets not compliant. To do so, we go to the policy center overview page by clicking on the governance icon and selecting policy center. Here we see the overview page and at the top left in the action required section. The open incidents display incidents themselves contain one or more assets that do not comply at the same time.
When a first run occurs, a single incident will be created for all assets that do not comply with the rules. However, after the initial run, the compliance checks occur nearly real time, so new incidents may only include a single asset. If it's metadata change it. No longer compliance or multiple assets if bulk uploads occur or a group of assets are moved into scope that do not comply. Clicking on this brings up the incident sidebar, which shows both open and closed incidents at the top filtering allows to show only open or closed incidents or even search for a specific incident based on the policy name.
01:00 — Incident details and the linked assets tab
The incident from our policy rules is here in open and clicking on it updates the side tab to give us the details. Here we see the policy name status owners reported by which since this is automated, it shows Atlan what rule was violated and when it was reported below. The activity shows the update on the incident showing currently just the incident being reported. To get into the details and the assets that are part of the incident, we clicked on the linked assets tab. Here we are presented with all the assets that have not complied with the rule outlined in the incident.
We can search or sort these results along with filtering based upon the asset type. Clicking on the first asset listed the side tab, updates to the asset details, and here we are able to validate that yes, this asset does not comply with our rule.
02:00 — Fixing an asset so it drops off the incident
We make a change to the metadata so that it complies. Click out of the side tab and back into our assets listed. If we then update our search filters, the search filtering updates, and we see that our asset is no longer included, as the incident is based on the rules, the compliance is automated, meaning that as Metta updates on those assets to actually comply, they automatically get removed from the incident. Saving us a ton of work from having to manually check off each asset while automated incidents are amazing. There may be a time where you want to log an incident manually, even if they don't fall out of complying with rules or if you did not create any rules on the policy itself.
This is done from the incident sidebar. In this case, we will create a new manual incident related to our policy. Clicking on the add new incident button opens the report. New incident side tab. In this case, let's say there was a single asset that wasn't included in the scope, but we want to ensure that it gets updated to adhere to our policy.
03:00 — Creating a manual incident for an asset
We fill out the description of the incident as additional asset scope, not complying, and a description of the incident that an additional asset needs to comply to this policy, but it wasn't in scope. Next we select the related policy, in this case, the policy we recently created. And finally we use the searching filters in the ad assets to include the exact assets that were impacted. Once done, we click Submit Incident to create the new incident with that asset linked the incident side tab, reloads and our new incident shows. Clicking on the incident brings the overview and one difference can be noted here for the manual incident versus the automated.
Since we manually created this one. There are no rules to validate whether or not the assets link now comply. So there is a change status option for the incident. Clicking on the change status brings the incident status change popup, where we can select the updated status, whether in process or closed. Along with adding a required note to give context, we update the status to close, stating that the asset now complies with the policy and click change status closing the incident.
04:00 — Changing an incident status to closed
With the ability to both automatically monitor and report incidents along with the ability to manually create them, we are now confident that we have our assets governed.

About this demo

Learn how to track, validate, and resolve open incidents triggered by policy rules in Atlan. This walkthrough shows how to view incident details, linked assets, and compliance checks, while also logging manual incidents when needed. Automated resolution ensures compliance updates are reflected in real-time, reducing manual effort.