{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":44299,"path":"security-management/security-incident-response/assessment-trigger-conditions-usecase.md","title":"Assessment trigger conditions examples","bundle":null,"doc_type":null,"release":"australia","body":"\n# Assessment trigger conditions examples\n\nThe following examples provide different scenarios on how mandatory and optional assessment trigger conditions are generated.\n\n-   On the Assessment Trigger Condition form, generate mandatory assessments when the **Priority** and **Business Impact** for a security incident is set to **Critical** on the **Assessment Trigger Rule** page. In such scenario, the security analysts cannot close the incident until the mandatory assessments are completed.\n-   If a security incident is in a **Review** state, security analysts cannot close the security incident without completing the **Post Incident Review Assessment**. An assessment link is available to take the assessment to the security analysts who are assigned \\(or who had requested for the assessment\\) to the incident.\n-   On the Assessment Trigger Condition form, generate optional assessments when the **Priority** and **Business Impact** for a security incident is set to **High**. In this example, if the security analysts do not complete the assessments and close the security incident, the assessments are automatically canceled.\n-   In case, if the mandatory or optional assessments does not match the security incident, assessments are not generated for such security incidents. A security analyst can close the security incident without completing the Post Incident Review assessment.\n\n"}}