Nightfall Documentation
  • Data Detection and Response
  • Posture Management
  • Data Exfiltration Prevention
  • Data Encryption
  • Developer APIs
  • Data Classification and Discovery
  • Data Discovery and Classification
  • Nightfall Audits
    • Introduction to Nightfall Audit
  • Google Drive Audit
    • Overview
    • Select Integration
    • Select Scope
    • Detection Rules
    • Automated Actions
    • Review Configurations
  • Analyzing Google Drive Audit Results
  • GitHub Audit
    • Overview
  • Select Integration
  • Configure Scope
  • Select Detection Rules
  • Review Configurations
Powered by GitBook
On this page
  • Use Cases for GitHub Audit: Hardcoded Secrets in GitHub Code
  • Prerequisites

Was this helpful?

Export as PDF
  1. GitHub Audit

Overview

PreviousAnalyzing Google Drive Audit ResultsNextSelect Integration

Last updated 22 days ago

Was this helpful?

This document explains the process of creating audits in Nightfall for the GitHub integration. A GitHub audit helps you analyze your historic GitHub data for the presence of sensitive content.

Use Cases for GitHub Audit: Hardcoded Secrets in GitHub Code

Modern applications store vast amounts of code in GitHub repositories, making manual scanning for sensitive data impractical. Nightfall audits can efficiently scan billions of bytes of code within minutes, quickly identifying hardcoded secrets such as passwords, API keys, and other sensitive credentials.

Prerequisites

You must ensure that the GitHub integration is installed in your Nightfall tenant. To learn more about how to install the GitHub integration, refer to this .

The process of creating an Audit for the GitHub integration involves the configuration of following settings.

  • Select Integration

  • Configure Scope

  • Select Detection Rules

  • Review Configurations

Nightfall documentation