GRC case summarization skill for privacy cases

  • Freigeben Version: Australia
  • Aktualisiert 12. März 2026
  • 3 Minuten Lesedauer

    • The GRC case summarization skill uses a large language model (LLM) to generate a structured summary of a privacy case record. The summary is generated on demand from case data and can be saved to the record for future reference.

    Overview of the GRC case summarization skill

    Privacy cases can involve multiple coordinators, complex activity logs, and breach assessments. The GRC case summarization skill generates a concise AI summary of key case details, so assignees and approvers can quickly understand the context and support efficient decision-making.

    The GRC case summarization skill collects data from predefined fields and related lists across the case record. This data is assembled into a prompt and sent to the configured LLM service provider, which then returns a structured summary.

    To summarize privacy case records, the skill must be activated from the Now Assist Admin console. Once it's activated, case analysts with the appropriate user role can trigger the skill on a privacy case.

    User roles

    Important user roles to activate and use this skill are:
    • sn_nowassist_admin.nsa_admin: Grants an admin access to activate or edit a Now Assist skill.
    • sn_privacy_case.privacy_case_analyst: Grants access to privacy case records.
    • sn_prm_gen_ai.user: Grants access to the Now Assist for Privacy Management skills.
      Hinweis:
      Users with the sn_prm_gen_ai.user role automatically have the sn_grc_sharegenai.grc_case_ai_user role, which is the minimum role required to use the GRC case summarization skill.

    All members of the Assignment group on a case record can view any summary that has been saved to that record.

    LLM service providers

    An administrator must set a default LLM provider before the skill can be used. The following providers are supported:

    • Azure OpenAI
    • AWS Claude
    • Now LLM Service
    • Now LLM Service LTS
    • Google Gemini

    To set a default provider for the GRC case summarization skill, see Manage model providers.

    Components of a privacy case summary

    The summary reflects case data at the time of generation. As the case progresses, you can regenerate the summary to capture the latest information. Once generated, you can review and edit the summary before saving it to the privacy case record. The saved summary appears in the Overview tab and in the Activity stream of the Details tab.

    Tabelle : 1. Privacy case summary structure
    Section What it captures
    Case Overview Core case details, such as name, description, start date, priority, and assigned analyst, captured from the Details tab.
    Events Timeline Date of occurrence, date of discovery, investigation start and end dates, and remediation start and end dates, captured from the Schedule section on the Details tab.
    Scope of Impact Blast Radius Breakdown- Summary of the areas and regulatory frameworks impacted by the privacy case, captured from the Impacted Areas, Related Areas, and Regulations tabs.
    • Impacted areas- Number of areas, such as control, entity, location, company, and users, impacted by the reported privacy case.
    • Related areas- Number of areas, such as policies, citations, control objectives, and risk events, related to the privacy case.
    • Regulations/Standards- Number of regulations that are or can be impacted by the reported privacy case.
    Data Impacted Types of personal data exposed or compromised during the incident, captured from the [PI] Information Objects tab.
    Evidence & Worknotes Work notes and comments recorded during the investigation, captured from the Activity section on the Details tab.
    Causes & Consequences Causes and consequences of the privacy case, captured from the Causes and Consequences tab.
    • Cause (Confirmed)- Confirmed cause of the incident.
    • Contributing Cause (Suspected)- Suspected cause of the incident.
    • Consequences- Resulting impact or penalties arising from the incident.
    Actions & Outcomes Summary of actions taken during the investigation, captured from the Action Tasks and Breach assessment tabs.
    • Investigation- Initial investigation tasks to examine the reported incident.
    • Assessment- Breach assessment to evaluate the risk and extent of compromised data.
    • Additional Actions Taken- Supplementary actions to support a resolution.
    Lessons Learned AI-powered analysis of the case timeline and overall investigation effort.
    • Velocity analysis- Time to detect, investigate, and remediate.
    • Investigation effort level- Effort assessment ranked as low, medium, or high, based on case complexity, activity log, and timelines.