Nightfall
HomeLoginDeveloper PlatformContact Us
Search…
Introduction
Why Cloud DLP?
Product Updates
Operationalizing DLP
Informing & Coaching Business Users
Running Historical Scans
Alert Management Guiding Principles
Integrating with Security Tools
Detection Engine
Getting Started
How Detection Works
Detectors
Detection Engine FAQs
Evaluating Detection
Nightfall for Slack
Nightfall for Slack: Demo Video
Getting Started
Alert Management
Remediation Guide
Nightfall for Slack Overview
FAQs
Nightfall for GitHub
Real-Time Scanning
Historical Scanning
Nightfall for GitHub Overview
Radar API Reference
Exporting Reports & Results
Integrating Webhook Endpoints
Integrating with Jira
Remediation Guide
Managed Services
FAQs
NIGHTFALL FOR GOOGLE DRIVE
Getting Started
Alert Management
Nightfall for Google Drive Overview
Remediation Guide
Historical Scanning
Demo Walkthrough Video
Nightfall for Confluence
FAQs
Getting Started
Real Time Scanning
Historical Scanning
Alert Management
Remediation Guide
Nightfall for Jira
Nightfall for Jira Overview
Jira Remediation Guide
Getting Started
Nightfall For Salesforce
Getting Started
FAQs
Account Management
User Administration
Authentication Options
Compliance
SOC 2 Compliance
HIPAA Compliance
PCI Compliance
Resources
FAQs
Login to Nightfall
Developer Platform
Platform Status
Contact Us
Powered By GitBook
Remediation Guide
Please see below for our best practices on how to remediate findings for Nightfall for Confluence.

​

Now that Confluence real-time remediation has been released, you can take manual and automated actions directly from the console or from your policy. For more info on your real time remediation options, please refer to the Product Update article below:

For historical scan results in Confluence, we recommend that you first group results by file and detector. Prioritize the Spaces/Pages with the most violations, open the Page, and delete the sensitive finding.
Delete all items that contain sensitive findings, including screenshots as well. This may be handled by your team, or by the end user, depending on your organization’s needs and access settings.
Note: Since we scan archived pages, but not previous versions of pages, we would recommend that when sensitive info is found, to remediate the info and then either delete each version in the history or to make a copy of the page and delete the original, which will remove the version history.
Questions to ask:
  1. 1.
    Is the sensitive data accurately identified?
  2. 2.
    Is it okay for the sensitive data to live on that page?
  3. 3.
    Is the data sample data?
  4. 4.
    Is the page archived?
  5. 5.
    Are there previous versions of the page that still contain the sensitive data?
If the data should not live in Confluence, ping the page author and ask them to remove or redact the data
In the findings file, we recommend marking each row as “No action needed” or “Resolved" to indicate that you have reviewed or addressed any violations.
For any further questions related to remediation or for Best Practices, please reach out to [email protected]
Nightfall for Confluence - Previous
Alert Management
Next - Nightfall for Jira
Nightfall for Jira Overview
Last modified 2mo ago
Copy link
On this page
Remediation in Confluence
Real time Scanning Remediation
Historical Scanning Remediation