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
  1. Core Features
  2. Governance
  3. Access

Policies and Alerting

Defining Policies

The Policies and Alerting feature within the LightBeam Governance module is a cornerstone of its data governance capabilities. It empowers organizations to define, enforce, and monitor data access policies, ensuring that sensitive information is accessed only by authorized individuals and in compliance with regulatory requirements. This section details the process of defining policies, configuring alerts, and managing policy violations.

Policies in the LightBeam Governance module are rules that dictate acceptable data access practices within an organization. These policies can be customized to address specific security requirements and compliance standards.

  • Types of Policies

    • Open Access Policy: Defines what constitutes open access to files. By default, any file accessible via a link is considered to have open access. This can be customized to tighten or loosen the criteria based on organizational needs.

    • Excessive Access Policy: Sets thresholds for what is considered excessive access to files. The default setting considers any file accessed by more than half of the total number of users as excessively accessed. This threshold can be adjusted to better fit the organization's security posture.

    • Cross-Departmental Access Policy: Controls access to sensitive data across different departments. For example, financial data should not be accessible to non-finance teams, and HR data should not be accessible to non-HR employees.

  • Creating Policies

    • Step 1: Define Criteria: Administrators define the criteria for each policy, specifying what conditions must be met for a policy to be considered violated.

    • Step 2: Assign Scope: Determine which data sources, user groups, and organizational units the policy applies to.

    • Step 3: Set Actions: Define the actions to be taken when a policy violation is detected, such as generating alerts, revoking access, or initiating automated remediation processes.

Configuring Alerts

Alerts are critical for real-time monitoring and response to policy violations. They ensure that administrators are promptly notified of any potential security issues.

  • Types of Alerts

    • Immediate Alerts: Triggered instantly when a policy violation is detected. These are used for critical issues that require immediate attention.

    • Threshold Alerts: Triggered when access reaches or exceeds a predefined threshold. For example, an alert can be set to trigger when a file is accessed by more than a specified number of users.

    • Scheduled Alerts: Generated based on scheduled scans and checks. These alerts provide regular updates on policy compliance and potential issues.

  • Setting up Alerts

    • Step 1: Define Alert Conditions: Specify the conditions under which an alert should be triggered. This can include criteria such as the type of data accessed, the number of users accessing the data, and the departments involved.

    • Step 2: Configure Notification Settings: Determine how alerts are communicated to administrators. Options include email notifications, SMS alerts, and dashboard notifications.

    • Step 3: Assign Alert Recipients: Designate the individuals or teams responsible for responding to alerts. This ensures that the right people are informed and can take action promptly.

Managing Policy Violations

Once policies and alerts are configured, the governance module continuously monitors data access to detect and manage policy violations.

  1. Detection:

    1. The module uses real-time monitoring and periodic scans to identify policy violations. This ensures that any unauthorized access or risky behavior is detected as soon as it occurs.

  2. Response:

    1. Automated Actions: Based on the defined policies, the module can automatically revoke access, block users, or move files to secure locations when a violation is detected.

    2. Manual Intervention: Administrators can review alerts and take manual actions as needed. This may involve investigating the root cause of the violation, contacting the affected users, or making adjustments to the access policies.

  3. Audit and Reporting:

    1. Violation Reports: Detailed reports on policy violations provide insights into the nature and frequency of violations, helping administrators understand trends and potential security gaps.

    2. Audit Trails: Comprehensive logs of all policy-related activities, including detected violations, triggered alerts, and actions taken. These logs support auditing and compliance efforts, ensuring that the organization can demonstrate adherence to data governance policies.

Monitoring and Reporting

Effective governance requires continuous monitoring and reporting to ensure compliance with defined policies and to identify potential security risks.

Dashboards

  • The governance module provides a comprehensive set of dashboards that display essential metrics, governance rule violations, and partner onboarding status.

  • Specific dashboards include the Main Dashboard, Governance Dashboard, Data Source Level Governance Dashboard, Per User View, and Entity View.

Reports

  • Detailed reports offer insights into high data access users, enabled rules, and rule violations at the data source level.

  • These reports can be used to audit data access, assess compliance with security frameworks, and identify areas for improvement.

PreviousAccess Governance at a Data Source LevelNextAccess Governance Statistics

Last updated 1 month ago

🧠
🛡️