{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":17882,"path":"governance-risk-compliance/privacy-workspace/act-ai-recco-rs-pia.md","title":"Accept or dismiss AI-recommended risk statements","bundle":null,"doc_type":null,"release":"australia","body":"\n# Accept or dismiss AI-recommended risk statements\n\nGenerate AI-assisted recommendations while reviewing a privacy assessment to quickly identify relevant risk statements from the privacy library.\n\n## Before you begin\n\nThe assessment task must be in Review state.\n\nRole required: sn\\_privacy.analyst, sn\\_prm\\_gen\\_ai.user\n\n**Note:** Without the sn\\_prm\\_gen\\_ai.user role, the privacy analyst reviewing the assessment can't generate AI recommendations.\n\n## About this task\n\nAfter a business user submits a privacy assessment, the assessment task moves to the Review state. As the assigned analyst on the assessment task, generate AI recommendations to quickly surface relevant control objectives and risk statements based on the assessment responses. Accepting a recommendation automatically scopes that record to the processing activity when the assessment task closes, and maps corresponding risks and controls to it.\n\n**Note:** Review all AI-generated recommendations for accuracy.\n\nThe Risk Statement Recommender skill generates the risk statement recommendations. Each recommended risk statement includes related control objectives that help mitigate the identified risks. You can select these control objectives to scope them to the processing activity along with the risk statement.\n\nFor more information about the skill, see [AI reviewer assist for privacy assessment tasks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/privacy-workspace/ai-reccos-for-pia.md).\n\n## Procedure\n\n1.  Navigate to **Workspaces** &gt; **Privacy Workspace**.\n\n2.  Select the Tasks icon \\[Omitted image \"icon-tprm-ws-tasks.png\"\\] Alt text:.\n\n3.  In the My pending tasks tab, select **Privacy assessments**.\n\n4.  Open the privacy assessment to be reviewed.\n\n5.  On the Overview tab, select **Recommend**.\n\n    The Recommendations tab organizes results into two tabs, Control objectives and Risk statements. If the request is still in progress, reload the page after some time. The request might take longer depending on the volume of data the skill processes. If no relevant data is available, the tab indicates that the request was completed and there are no recommendations currently available.\n\n6.  To review the risk statement recommendations, select the Risk statements tab.\n\n7.  Select a risk statement recommendation card to review.\n\n    Each card displays:\n\n<table id=\"id_b2w_dgj_jkc\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nName\n\n</td><td>\n\nName of the risk statement.\n\n</td></tr><tr><td>\n\nCategory\n\n</td><td>\n\nBusiness or technical domain for the risk statement.\n\n</td></tr><tr><td>\n\nClassification\n\n</td><td>\n\nFunctional intent of the risk statement.\n\n</td></tr><tr><td>\n\nAI suggestion guide\n\n</td><td>\n\nReason for recommending the risk statement. It references the specific assessment responses and record context that contributed to the recommendation.**Note:** Review AI-generated content for accuracy.\n\n</td></tr><tr><td>\n\nDescription\n\n</td><td>\n\nDescription and summary of the risk statement.\n\n</td></tr><tr><td>\n\nReview and accept mitigating controls\n\n</td><td>\n\nControl objectives that are mapped to this risk statement in the privacy library and are also recommended for the current assessment. The records that are mapped in the library but not recommended for this assessment don't appear here.For example, a risk statement might have five mitigating control objectives mapped to it in the library. If only one of those was recommended for this assessment, only that control objective is listed for selection.\n\n</td></tr></tbody>\n</table>8.  View the risk statement in the privacy library or refresh your recommendations.\n\n    |Option|Description|\n    |------|-----------|\n    |**Select the details icon \\[Omitted image \"details-icon.jpg\"\\] Alt text:.**|View details of the record in the privacy library.|\n    |**Select the refresh icon \\[Omitted image \"refresh-icon.jpg\"\\] Alt text:.**|Refresh the recommendations to reflect the latest data.|\n\n9.  To scope related control objectives with the recommended risk statement, select records in New state from the Control objective sub-tab of **Review and accept mitigating controls**.\n\n    When you accept the risk statement, any selected control objectives are accepted with it. This control-to-risk mapping carries over to the processing activity record after the assessment is closed.\n\n    **Note:** The State column shows Accepted for a control objective that is already in Applicable scope, and New for those that haven't been acted on yet.\n\n    \\[Omitted image \"ai-recco-co-in-rs-pia.png\"\\] Alt text: Review and accept mitigating controls section in a risk statement recommendation card for a privacy assessment\n\n10. Accept or dismiss the recommendation.\n\n    -   If the recommendation is relevant, select **Accept**, then select **Accept and add** to confirm.\n    -   If the recommendation isn't relevant, select **Dismiss**, then select **Confirm**.\n    An accepted risk statement, and any control objectives you selected with it, are automatically added to the Applicable scope tab of the assessment task. A dismissed risk statement results in any related control objectives you selected to be dismissed with it.\n\n11. To change your decision on an accepted or dismissed recommendation, select the card, then select **Revert**.\n\n\n## Result\n\nRecords scoped to a processing activity based on assessment responses appear in the Applicable scope tab of the assessment task. These include accepted AI recommendations, records added manually, and records added through smart assessment automation rules. To verify that the accepted risk statement recommendations appear in the list correctly, filter by **AI-assisted** in the Mode column. Any control objective you selected with the accepted risk statement also appears in this tab. Any control objective you selected with the accepted risk statement also appears in this tab. If you must add more records, you can manually add those to the tab.\n\n**Note:** If a recommended record is already in Applicable scope from another mode such as automation, accepting the recommendation does not create a duplicate. The Mode column retains the value of the original source. If that record is later removed from Applicable scope and you then accept the same recommendation, the record is added back with **AI-assisted** as its mode.\n\n## What to do next\n\nReview the control objective recommendations. For steps, see [Accept or dismiss AI-recommended control objectives](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/privacy-workspace/act-ai-recco-co-pia.md). After reviewing all recommendations, mark the assessment as complete. For steps, see [Review a privacy assessment](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/privacy-workspace/review-a-privacy-assessment.md).\n\nClosing the assessment task scopes the accepted recommendations to the processing activity:\n\n-   The corresponding risk for the accepted risk statement is added to the Risks tab of the processing activity.\n-   The corresponding controls from the accepted control objectives are added to the Controls tab of the processing activity.\n-   The same controls are also mapped to the corresponding risk record in the processing activity, carrying over the control-to-risk mapping from the assessment task.\n\n"}}