Agent skill

Breach Detection System

by mukul975 in mukul975/Privacy-Data-Protection-Skills

Implements technical breach detection capabilities including SIEM integration, DLP alert configuration, anomaly detection rules, and insider threat monitoring.

Apache-2.0Auto-check passedSecurity

Install Breach Detection System

skills CLI
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill breach-detection-system -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Privacy-Data-Protection-Skills breach-detection-system --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy/breach-detection-system .claude/skills/breach-detection-system && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
breach-detection-system
GitHub stars
297
Token cost
~3k tokens
SKILL.md length
1,072 words
Files
5 (incl. scripts, references, assets)
Skills in repo
280
Repo updated
First seen
Licence
Apache-2.0

At a glance

Implements technical breach detection capabilities including SIEM integration, DLP alert configuration, anomaly detection rules, and insider threat monitoring.

  • Works in 5 steps: SIEM correlation rule or DLP policy… → Alert is enriched with contextual data:… → If the affected system is classified as… → …
  • Tasks that involve Security operations
  • SKILL.md covers Overview, Breach Classification Taxonomy, SIEM Integration Architecture and DLP Alert Configuration, plus 3 more sections
  • Runs Python scripts from its folder

What it does

Breach Detection System is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements technical breach detection capabilities including SIEM integration, DLP alert configuration, anomaly detection rules, and insider threat monitoring. Provides a breach classification taxonomy across confidentiality, integrity, and availability dimensions. Covers detection tool selection, alert tuning, and integration with privacy incident response workflows. Keywords: breach detection, SIEM, DLP, anomaly detection, insider threat, classification.

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/standards.md` and `references/workflows.md`).

It sits in Security, covering Security operations, Anomaly detection and Privacy and GDPR. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Security operations
  • Tasks that involve Anomaly detection
  • Tasks that involve Privacy and GDPR

Example prompts

  • “Use the breach-detection-system skill to implement technical breach detection capabilities including SIEM integration, DLP alert configuration…”
  • “/breach-detection-system”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. SIEM correlation rule or DLP policy triggers an alert.
  2. Alert is enriched with contextual data: user identity, data classification of affected system, data subject count estimate.
  3. If the affected system is classified as containing personal data (tagged in the CMDB), the alert is automatically duplicated to the…
  4. Privacy incident coordinator performs initial triage within 30 minutes.
  5. If personal data breach is confirmed, the Art. 33 72-hour clock activation is triggered and the DPO is notified.

What it can do on your machine

Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Breach Detection System loads about 3k tokens when it runs, and up to ~5.8k if it reads all its reference files. Until then it costs about 121 tokens; SKILL.md has 1,072 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~121
When it runs · the whole SKILL.md, loaded when a task matches
~3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 1,072 words, ~2,962 tokens.

Download SKILL.mdSave it as .claude/skills/breach-detection-system/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
breach-detection-system
description
Implements technical breach detection capabilities including SIEM integration, DLP alert configuration, anomaly detection rules, and insider threat monitoring. Provides a breach classification taxonomy across confidentiality, integrity, and availability dimensions. Covers detection tool selection, alert tuning, and integration with privacy incident response workflows. Keywords: breach detection, SIEM, DLP, anomaly detection, insider threat, classification.
license
Apache-2.0
metadata.author
mukul975
metadata.version
1.0
metadata.domain
privacy
metadata.subdomain
data-breach-response
metadata.tags
breach-detection, siem, dlp, anomaly-detection, insider-threat, classification

Implementing Breach Detection System

Overview

Effective breach detection is the prerequisite for timely Art. 33 notification. The GDPR does not prescribe specific detection technologies, but Art. 32 requires appropriate technical and organisational measures, and Art. 33(1) creates a de facto obligation to detect breaches promptly — a controller cannot notify within 72 hours if it takes months to discover a breach. This skill covers the technical architecture for personal data breach detection, including SIEM integration, DLP alerting, behavioral analytics, and insider threat monitoring.

Breach Classification Taxonomy

Level 1: CIA Triad Classification
TypeDefinitionDetection Method
ConfidentialityUnauthorized disclosure or access to personal dataDLP alerts, access log anomalies, data exfiltration detection
IntegrityUnauthorized modification of personal dataFile integrity monitoring, database audit logs, checksum validation
AvailabilityLoss of access to or destruction of personal dataSystem health monitoring, backup verification, ransomware detection
Level 2: Attack Vector Classification
VectorDescriptionPrimary Detection
External attackUnauthorized access from outside the network perimeterIDS/IPS, firewall logs, authentication failures
Insider threatAuthorized user acting beyond their authorized scopeUEBA, DLP, access pattern analysis
Third-party compromiseBreach originating from a processor or vendorVendor monitoring, API anomaly detection
Accidental disclosureHuman error leading to data exposureDLP content inspection, email gateway filters
System failureTechnical failure causing data loss or corruptionInfrastructure monitoring, backup validation
Physical breachLoss or theft of physical devices containing dataAsset tracking, device encryption verification
Level 3: Data Sensitivity Classification
LevelData TypesDetection Priority
CriticalArt. 9 special categories, Art. 10 criminal data, financial credentialsReal-time alerting, immediate escalation
HighGovernment identifiers, financial account data, authentication credentialsReal-time alerting, 15-minute escalation
MediumContact details, employment records, purchase historyNear-real-time (5-minute batching), 1-hour escalation
LowPublicly available business contact data, non-personal metadataBatch processing (hourly), daily review

SIEM Integration Architecture

Event Source Configuration

Stellar Payments Group deploys Splunk Enterprise Security as the primary SIEM platform. The following log sources are ingested for breach detection:

SourceLog TypeIngestion MethodEvents/Day
Active DirectoryAuthentication, authorization, group changesSplunk Universal Forwarder2.4M
AWS CloudTrailAPI calls, console logins, resource changesS3-to-Splunk via SQS8.7M
PostgreSQL auditQuery logs, schema changes, failed authenticationssyslog-ng to Splunk HEC14.2M
Palo Alto PA-5260Firewall sessions, URL filtering, threat preventionsyslog to Splunk45.3M
CrowdStrike FalconEndpoint detections, process execution, file writesFalcon SIEM Connector6.1M
Microsoft 365Email audit, SharePoint access, Teams DLPMicrosoft Graph API via Splunk Add-on3.8M
OktaSSO authentications, MFA events, admin changesOkta Event Hook to Splunk HEC890K
AWS GuardDutyThreat intelligence findings, anomaly detectionsCloudWatch to Splunk12K
Correlation Rules for Breach Detection
Rule 1: Mass Data Access Anomaly
Trigger: Single user account accesses more than 500 unique personal data records within a 30-minute window.
Data sources: PostgreSQL audit logs, application access logs.
Severity: High
Action: Create incident ticket, alert SOC analyst, notify DPO on-call.
False positive mitigation: Whitelist batch processing service accounts (reviewed quarterly). Flag whitelisted accounts if access occurs outside scheduled batch windows.
Rule 2: Data Exfiltration Indicator
Trigger: Outbound data transfer exceeding 50MB to an unclassified external destination from a system containing personal data.
Data sources: Palo Alto firewall, CrowdStrike network telemetry, DLP alerts.
Severity: Critical
Action: Automated network isolation of source endpoint, SOC analyst investigation, DPO notification.
False positive mitigation: Baseline normal data transfer patterns per endpoint. Whitelist approved SaaS destinations (Salesforce, Workday, etc.).
Rule 3: Privileged Account Anomaly
Trigger: Database administrator account performs SELECT queries on personal data tables outside of change management windows OR from an unrecognized source IP.
Data sources: PostgreSQL audit logs, Okta authentication logs, IP geolocation.
Severity: High
Action: Alert SOC lead and database security team. Log full query text for forensic review.
Rule 4: Ransomware Behavior Pattern
Trigger: More than 20 file rename/encrypt operations per second on file servers or database storage volumes, OR known ransomware file extension creation (.lockbit, .encrypted, .crypt).
Data sources: CrowdStrike Falcon, Windows file audit logs, storage IOPS monitoring.
Severity: Critical
Action: Automated isolation of affected system, activate incident response team, preserve forensic image.
Rule 5: Authentication Brute Force
Trigger: More than 50 failed authentication attempts against personal data systems within 10 minutes from a single source, OR more than 200 failed attempts across multiple accounts from the same source within 30 minutes (password spray).
Data sources: Active Directory, Okta, application authentication logs.
Severity: Medium (escalates to High if followed by successful authentication).
Action: Block source IP at firewall, SOC investigation, check for compromised credentials.

DLP Alert Configuration

Email DLP Policies
Policy NameDetection ContentActionSeverity
PII OutboundRegex: German ID (Personalausweisnummer), IBAN, credit card numbers, health insurance numbersBlock + encrypt + alert DPOHigh
Bulk PIIMore than 10 rows of structured personal data (name + email/phone/address) in email body or attachmentBlock + alert sender manager + SOCCritical
Special CategoryKeywords/patterns matching health diagnoses, genetic markers, biometric templates, trade union referencesBlock + alert DPOCritical
Cross-Border TransferPersonal data sent to recipients in non-adequate countries without approved transfer mechanismHold for review + alert privacy teamMedium
Endpoint DLP Policies
Policy NameDetection ContentAction
USB Copy PIICopy of files containing personal data to removable mediaBlock (exceptions via DPO-approved ticket)
Cloud Upload PIIUpload of personal data files to non-approved cloud servicesBlock + alert SOC
Print PII BulkPrint job containing more than 50 records of personal dataAlert line manager + SOC
Screenshot PIIScreen capture of application displaying personal data recordsLog + alert SOC (for pattern analysis)

Anomaly Detection and UEBA

Show full SKILL.md (444 more words)Show less
Behavioral Baselines

User and Entity Behavior Analytics (UEBA) establishes normal patterns for each user and system account:

Baseline MetricNormal RangeAnomaly ThresholdDetection Window
Daily record access countPer-user historical average3x standard deviation above meanRolling 30-day baseline
Access time patternsHistorical working hoursAccess outside 95th percentile time rangeRolling 90-day baseline
Data download volumePer-user historical average2x standard deviation above mean for 2+ consecutive hoursRolling 14-day baseline
Geographic access locationHistorical IP geolocationNew country not seen in 90-day historyRolling 90-day baseline
Application access patternHistorical application mixAccess to new personal data application not in 60-day historyRolling 60-day baseline
Insider Threat Indicators

Composite risk scoring for insider threat detection combines multiple low-severity indicators:

IndicatorWeightSource
Access outside normal hours to personal data systems15Okta + application logs
Bulk data download from HR or customer databases25DLP + database audit
Use of personal email or cloud storage from corporate device10CrowdStrike + proxy logs
Notice period or performance improvement plan status20HR system integration (Workday)
Access to data outside role scope20Role-based access comparison
Disabling or circumventing security controls30Endpoint agent tampering alerts
Repeated failed access to restricted personal data10Application access logs

Composite scores above 60 trigger enhanced monitoring. Scores above 80 trigger SOC analyst investigation and DPO notification.

Integration with Privacy Incident Response

Automated Workflow
  1. SIEM correlation rule or DLP policy triggers an alert.
  2. Alert is enriched with contextual data: user identity, data classification of affected system, data subject count estimate.
  3. If the affected system is classified as containing personal data (tagged in the CMDB), the alert is automatically duplicated to the privacy incident queue in ServiceNow.
  4. Privacy incident coordinator performs initial triage within 30 minutes.
  5. If personal data breach is confirmed, the Art. 33 72-hour clock activation is triggered and the DPO is notified.
Detection-to-Notification Timeline Target
PhaseTargetOwner
Detection to alertUnder 5 minutesSIEM platform (automated)
Alert to triageUnder 30 minutesSOC analyst
Triage to breach confirmationUnder 4 hoursSOC lead + privacy coordinator
Breach confirmation to DPO notificationUnder 1 hourPrivacy incident coordinator
DPO notification to 72-hour clock startImmediateDPO

Monitoring and Tuning

Monthly Review Cadence
  1. Review false positive rates for all breach detection correlation rules. Target: under 15% false positive rate.
  2. Analyze detection gap assessments against known breach scenarios from EDPB Guidelines 01/2021.
  3. Update behavioral baselines following organizational changes (new hires, departures, role changes).
  4. Validate that all new personal data systems have been onboarded to the SIEM and DLP platforms.
  5. Test end-to-end detection-to-notification workflow with a simulated breach scenario quarterly.

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/breach-detection-system of mukul975/Privacy-Data-Protection-Skills.

  • SKILL.md
  • assets/template.md
  • references/standards.md
  • references/workflows.md
  • scripts/process.py

Open the folder on GitHubat commit 9b2ef9e

Compare with similar skills

Breach Detection System next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Breach Detection System compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Breach Detection System this skillmukul975/Privacy-Data-Protection-Skills297—~3kAutomated safety check: PassApache-2.0
Kubernetes Network Security Auditkubeshark/kubeshark12k—~7.3kAutomated safety check: NotesApache-2.0
Hunting For Webshell Activitymukul975/Anthropic-Cybersecurity-Skills34k—~904Automated safety check: PassApache-2.0
Configuring Suricata For Network Monitoringmukul975/Anthropic-Cybersecurity-Skills34k—~3.6kAutomated safety check: NotesApache-2.0
Detecting Network Anomalies With Zeekmukul975/Anthropic-Cybersecurity-Skills34k—~3.6kAutomated safety check: NotesApache-2.0
Implementing Soar Automation With Phantommukul975/Anthropic-Cybersecurity-Skills34k—~3.6kAutomated safety check: PassApache-2.0

Similar skills

  • Hunts for compromised workloads and malicious traffic in a Kubernetes cluster by sweeping network data through Kubeshark MCP, mapped to MITRE ATT&CK.

    12k GitHub stars~7.3k tokensUpdated yesterday
    SecurityAuto-check: notes
  • Hunting For Webshell Activity

    mukul975/Anthropic-Cybersecurity-Skills

    Runs a hypothesis-driven threat hunt for web shell deployment (T1505.003) on internet-facing servers by analyzing file creation in web directories, suspicious child-process spawning from web server…

    34k GitHub stars~904 tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Configuring Suricata For Network Monitoring

    mukul975/Anthropic-Cybersecurity-Skills

    Deploys and configures Suricata IDS/IPS with Emerging Threats rulesets, EVE JSON logging, and custom rules for high-throughput, protocol-aware traffic inspection (HTTP, TLS, DNS, SMB) and SIEM…

    34k GitHub stars~3.6k tokensUpdated 1 mo ago
    SecurityAuto-check: notes
  • Detecting Network Anomalies With Zeek

    mukul975/Anthropic-Cybersecurity-Skills

    Deploy and configure Zeek (formerly Bro) to passively analyze network traffic, generate structured connection/DNS/HTTP/SSL/file logs, detect anomalous behavior, and write custom scripts for…

    34k GitHub stars~3.6k tokensUpdated 1 mo ago
    SecurityAuto-check: notes
  • Implementing Soar Automation With Phantom

    mukul975/Anthropic-Cybersecurity-Skills

    Implements Security Orchestration, Automation, and Response (SOAR) workflows using Splunk SOAR (formerly Phantom) to automate alert triage, IOC enrichment, containment actions, and incident response…

    34k GitHub stars~3.6k tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Threat Detection

    alirezarezvani/claude-skills

    A skill your agent uses when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.

    28k GitHub stars~3.5k tokensUpdated 1 mo ago
    SecurityAuto-check passed

More from mukul975/Privacy-Data-Protection-Skills

All 280 skills in this repo
  • Age Gating Services

    mukul975/Privacy-Data-Protection-Skills

    Implements age-gating mechanisms for online services to restrict access based on user age.

    297 GitHub stars~3.7k tokensUpdated 6 mo ago
    Auto-check passed
  • AI Data Retention

    mukul975/Privacy-Data-Protection-Skills

    Manages AI model retention and machine unlearning requirements.

    297 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed
  • AI Dpia

    mukul975/Privacy-Data-Protection-Skills

    Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.

    297 GitHub stars~3.4k tokensUpdated 6 mo ago
    Auto-check passed
  • Dpia Mitigation Plan

    mukul975/Privacy-Data-Protection-Skills

    Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).

    297 GitHub stars~846 tokensUpdated 6 mo ago
    Auto-check passed
  • Gdpr Accountability

    mukul975/Privacy-Data-Protection-Skills

    Guides implementation of the GDPR accountability principle under Articles 5(2) and 24, including documentation requirements for policies, DPIAs, RoPA, training records, and breach logs.

    297 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed
  • Pia Threshold Screening

    mukul975/Privacy-Data-Protection-Skills

    Conducts pre-DPIA threshold screening to determine whether a full Data Protection Impact Assessment is required under GDPR Article 35.

    297 GitHub stars~880 tokensUpdated 6 mo ago
    Auto-check passed

Questions about Breach Detection System

What does Breach Detection System do?

Implements technical breach detection capabilities including SIEM integration, DLP alert configuration, anomaly detection rules, and insider threat monitoring. Breach Detection System is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements technical breach detection capabilities including SIEM integration, DLP alert configuration, anomaly detection rules, and insider threat monitoring.

When should I use Breach Detection System?

Breach Detection System fits situations like: tasks that involve Security operations; tasks that involve Anomaly detection; tasks that involve Privacy and GDPR.

How do I install Breach Detection System in Claude Code?

Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill breach-detection-system -a claude-code`. Or copy the skill folder (skills/privacy/breach-detection-system in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/breach-detection-system in your project. Claude Code loads it when a task matches its description.

How do I install Breach Detection System in Codex?

Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill breach-detection-system -a codex`. Or copy the skill folder (skills/privacy/breach-detection-system in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/breach-detection-system in your project. Codex loads it when a task matches its description.

Can I use Breach Detection System in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill breach-detection-system -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/breach-detection-system, .gemini/skills/breach-detection-system, .github/skills/breach-detection-system and .opencode/skills/breach-detection-system in your project.

What does Breach Detection System need to run?

Going by SKILL.md and its folder, Breach Detection System needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Breach Detection System access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Breach Detection System safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Breach Detection System use?

Breach Detection System is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Breach Detection System use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.8k tokens, read only when the agent opens those files.

What are the alternatives to Breach Detection System?

Skills that share tags, products or a category with Breach Detection System: Kubernetes Network Security Audit (kubeshark/kubeshark, 12k stars), Hunting For Webshell Activity (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Configuring Suricata For Network Monitoring (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Detecting Network Anomalies With Zeek (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Breach Detection System?

mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 297 GitHub stars. The repository holds 280 skills in this directory. The repository was last updated on March 16, 2026.

Source: mukul975/Privacy-Data-Protection-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.