LightBeam Documentation
Installer GuidesData SourcesPlaybooksInsightsPrivacyOpsGovernance
  • 💡What is LightBeam?
  • 🚀Getting Started
    • ⚙️Installer Guides
      • Pre-Requisites / Security Configurations
        • Firewall Requirements
        • Securing LightBeam on EKS with AWS Certificate Manager on Elastic Load Balancer
        • Configure HTTPS for LightBeam Endpoint FQDN Standalone deployment
        • Using Custom Certificates with LightBeam
        • Securing LightBeam on GKE with Google Certificate Manager and GCE Ingress
      • Core
        • LightBeam Deployment Instructions
        • LightBeam Installer
        • Web App Deployment
        • LightBeam Diagnostics
        • LightBeam Cluster Backup & Restore using Velero
      • Platform Specific
        • AWS
        • Microsoft Azure
        • Google Cloud (GKE)
        • Standalone Virtual Machine
        • Deployment on an Existing Managed Kubernetes Cluster
        • Azure Marketplace Deployment
      • Integration and Setup
        • Setting Up AWS PrivateLink for RDS-EKS Interaction
        • Twingate and LightBeam Integration Guide
        • Data Subject Request Web Application Server
        • Generate CSR for LightBeam
  • 🧠Core Features
    • 🔦Spectra AI
      • 🔗Data Sources
        • Cloud Platforms
          • AWS Auto Discovery
          • GCP Auto Discovery
        • Databases and Datalakes
          • PostgreSQL
          • Aurora (PostgreSQL)
          • Snowflake
          • MS SQL
          • MySQL
          • Aurora (MySQL)
          • BigQuery
          • AWS Redshift
          • Oracle
          • DynamoDB
          • MongoDB
          • CosmosDB (PostgreSQL)
          • CosmosDB (MongoDB)
          • CosmosDB (NoSQL)
          • Looker
          • AWS Glue
          • Databricks
          • SAP HANA
          • CSV Files as a Datasource
        • Messaging
          • Gmail
          • Slack
          • MS Teams
          • MS Outlook
        • Developer Tools
          • Zendesk
          • ServiceNow
          • Jira
          • GitHub
          • Confluence
        • File Repositories
          • NetDocuments
          • AWS S3
          • Azure Blob
          • Google Drive
          • OneDrive
          • SharePoint
          • Viva Engage
          • Dropbox
          • Box
          • SMB
        • CRM
          • Hubspot
          • Salesforce
          • Automated Data Processing (ADP)
          • Marketo
          • Iterable
          • MS Dynamics 365 Sales
          • Salesforce Marketing Cloud
      • 🔔PlayBooks
        • What is LightBeam Playbooks?
        • Policy and Alerts
          • Types of Policies
          • How to create a rule set
            • File Extension Filter
          • Configuring Retention Policies
          • Viewing Alerts
          • Sub Alerts
            • Reassigning Sub-Alerts
            • Sub-alert States
          • Levels of Actions on Alerts
          • User Roles and Permissions
            • Admin View
            • Alert Owner View
            • Onboarding New Users
              • User Management
              • Okta Integration
              • Alert Assignment Settings
              • Email Notifications
            • Planned Enhancements
          • Audit Logs
          • No Scan List
          • Permit List
          • Policy in read-only mode
      • 📊Insights
        • Entity Workflow
        • Document Classification
        • Attribute Management Overview
          • Attributes Page View
          • Attribute Sets
          • Creating Custom Attribute
          • Attributes List
        • Template Builder
        • Label Management
          • MIP Integration
          • Google Labels Integration
      • 🗃️Reporting
        • Delta Reporting
        • Executive Report
        • LightBeam Lens
      • Scanning and Redaction of Files
        • On-demand scanning
      • How-to Guides
        • Leveraging LightBeam insights for structured data sources
      • LightBeam Dashboard Outlay
      • Risk Score
    • 🏛️PrivacyOps
      • Data Subject Request (DSR)
        • What is DSR?
        • Accessing the DSR Module
        • DSR Form Builder (DPO View)
          • Creating a New DSR Form
            • Using a Predefined Template
            • Creating a Custom Form
          • Form Configuration
          • Form Preview and Publishing
          • Multi-Form Management
          • Messaging Templates
        • Form Submission & Email Verification (Data Subject View)
        • DSR Management Dashboard (DPO View)
        • Processing DSR Requests
          • Data Protection Officer (DPO) Workflow
          • Self Service Workflow (Direct Validation)
          • Data Source Owner (DSO) Workflow
        • DSR Report
      • 🚧Consent Management
        • Overview
        • Consent Logs
        • Preference Centre
        • Settings
      • 🍪Cookie Consent
        • Dashboard
        • Banners
        • Domains
        • Settings
        • CMP Deployment Guide for Google Tag Manager
        • FAQs
      • 🔏Privacy Impact Assessment (PIA)
        • PIA Templates
        • PIA Assessment Workflow
        • Collaborator View
        • Process Owner Login View (With Collaborator)
        • Filling questionnaire without collaborator
        • Submitting the assessment for DPO review
        • DPO review process
        • Marking the assessment as reviewed
        • Editing and resubmitting assessments after DPO review
        • Revoke review request
        • Edit Reviewer
        • PIA Reports
      • ⏺️Records of Processing Activity (RoPA)
        • Creating a RoPA Template
          • How to clone a template
          • How to use a template
        • How to create a process
          • Adding Process Details
          • Adding Data Elements
          • Adding Data Subjects
          • Adding Data Retention
          • Adding Safeguards
          • Adding Transfers
          • Adding a Custom Section
          • Setting a Review Schedule
          • Data Flow Diagram
        • How to add a collaborator
        • Overview Section
        • Generating a RoPA Report Using LightBeam
        • Collaborator working on a ticket
    • 🛡️Governance
      • Access
        • Dashboard
        • Users
        • Groups
        • Objects
        • Active Directory Settings
        • Access Governance at a Data Source Level
        • Policies and Alerting
        • Access Governance Statistics
        • Governance Module Dashboard
      • Privacy At Partners
  • 📊Tools & Resources
    • 🔀API Documentation
      • API to Create Reports for Structured Datasource
    • ❓Onboarding Assessments
      • Structured Datasource Onboarding Questionnaire
        • MongoDB/CosmosDB Questionnaire
        • Oracle Datasource Questionnaire
      • SMB Questionnaire
    • 🛠️Administration
      • Audit Logs
      • SMTP
        • Basic and oAuth Configuration
      • User Management
        • SAML Identity Providers
          • Okta
            • LightBeam Okta SAML Configuration Guide
          • Azure
            • Azure AD SAML Configuration for LightBeam
          • Google
            • Google IDP
        • Local User Management
          • Adding a User to the LightBeam Dashboard
          • Reset Default Admin Password
  • 📚Support & Reference
    • 📅Release Notes
      • LightBeam v2.2.0
      • Reporting Release Notes
      • Q1 2024 Key Enhancements
      • Q2 2024 Key Enhancements
      • Q3 2024 Key Enhancements
      • Q4 2024 Key Enhancements
    • 📖Glossary
Powered by GitBook
On this page
  • Overview of Sub-alert States
  • Managing Sub-alert States
  • Bulk State Changes
  • Viewing Sub-alert States
  • Audit Trail for State Changes
  • Use Cases for Sub-alert States
  1. Core Features
  2. Spectra AI
  3. PlayBooks
  4. Policy and Alerts
  5. Sub Alerts

Sub-alert States

PreviousReassigning Sub-AlertsNextLevels of Actions on Alerts

Last updated 1 month ago

In LightBeam Playbooks Alerts 2.1.2, 'Sub-alert States' have been introduced to facilitate workflow management between multiple stakeholders during the alert review process. This feature allows you to move a sub-alert through different states while it remains active.

Overview of Sub-alert States

When a sub-alert is first generated, it is marked as Open. From there, you can transition the sub-alert through various states:

  • Open: Initial state when a sub-alert is created

  • In Progress: Sub-alert is being actively worked on

  • In Review: Sub-alert has been submitted for review

  • Review Completed: Review process has been completed

  • On Hold: Processing of the sub-alert has been temporarily paused

Figure 36: Sub-alert State Flow

Managing Sub-alert States

To change a sub-alert's state:

  1. Navigate to the sub-alert in the 'Objects Impacted' table.

  2. Select the sub-alert by clicking the checkbox next to it.

  3. Click on the "Change State" action in the actions menu above the table.

Figure 37: Change State Action

  1. In the dialog that appears, select the desired state from the available options.

Figure 38: State Selection Dialog

  1. Click "Apply" to change the state.

  2. The state change will be recorded in the audit log with details of the user who performed the action.

Bulk State Changes

You can also perform state changes on multiple sub-alerts simultaneously:

  1. In the 'Objects Impacted' table, use the state filter dropdown to find sub-alerts in specific states if needed.

Figure 39: Sub-alert State Filter

  1. Select multiple sub-alerts by clicking the checkboxes next to them.

  2. If you want to select all sub-alerts visible on the current page, click the checkbox in the table header.

  3. If you want to select all sub-alerts across all pages, click the "Select all sub-alerts" option that appears after selecting the header checkbox.

Figure 40: Select All Sub-alerts Option

  1. Click "Change State" from the actions menu.

  2. Select the target state for all selected sub-alerts.

  3. Click "Apply" to change the state of all selected sub-alerts.

Viewing Sub-alert States

The current state of each sub-alert is displayed in the 'Objects Impacted' table. You can:

  1. Sort sub-alerts by their state by clicking on the state column header.

  2. Filter sub-alerts by specific states using the state filter dropdown.

  3. View state change history in the audit logs.

Audit Trail for State Changes

All state changes are recorded in the audit logs with the following information:

  • User who performed the state change

  • Previous state

  • New state

  • Timestamp of the change

  • Affected sub-alerts

Figure 41: Audit Log Entry for State Change

Note: Once a sub-alert is closed (resolved, permitted, or muted), its state cannot be changed and it will no longer appear in the active sub-alerts view.

Use Cases for Sub-alert States

The sub-alert states feature supports various workflow scenarios, such as:

  1. Security Review Workflow:

    • Security analyst sets state to "In Progress" while working on the alert

    • When ready for review, changes state to "In Review"

    • Security manager reviews and changes state to "Review Completed"

  2. Compliance Verification:

    • Compliance officer reviews sub-alerts marked as "In Review"

    • After verification, changes state to "Review Completed"

  3. Investigation Workflow:

    • Initial triage sets sub-alert to "In Progress"

    • If waiting for additional information, sets to "On Hold"

    • Once investigation continues, returns to "In Progress"

    • When ready for final review, sets to "In Review"

The sub-alert states feature enables better collaboration and tracking of alert review processes, allowing multiple stakeholders to coordinate their efforts in addressing data privacy incidents.

🧠
🔦
🔔