data-classification
Skill0 starsChanged 11 days agoMITView on GitHub
Design and operationalize a data classification scheme — levels and handling rules, sensitivity labels (Microsoft Purview, Google Drive labels), auto-labelling with sensitive information types, default labels and encryption — and measure adoption. Use when creating or revising classification policy, deploying labels, or deciding how a data set must be protected.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Happy-Technologies-LLC/happy-platform-skillstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Happy-Technologies-LLC/happy-platform-skills★ 41same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository273 other files it gives its agents.
- ad-attack-path-analysisSkill
- adcs-security-reviewSkill
- ad-privileged-access-reviewSkill
- dcsync-detectionSkill
- gpo-security-reviewSkill
- kerberos-attack-detectionSkill
- agent-tool-permission-reviewSkill
- ai-incident-responseSkill
- llm-gateway-controlsSkill
- llm-security-evaluationSkill
- mcp-server-security-reviewSkill
- model-artifact-securitySkill
- prompt-injection-reviewSkill
- rag-security-reviewSkill
- api-abuse-detectionSkill
- api-authorization-testingSkill
- api-inventorySkill
- api-schema-securitySkill
- dast-baselineSkill
- sast-triageSkill
- sca-dependency-riskSkill
- secure-code-reviewSkill
- security-requirementsSkill
- threat-modelingSkill
- asset-criticality-tieringSkill
- asset-inventory-reconciliationSkill
- external-attack-surface-reviewSkill
- shadow-it-discoverySkill
- aws-credential-compromiseSkill
- aws-iam-reviewSkill
- aws-org-guardrailsSkill
- cloudtrail-investigationSkill
- guardduty-triageSkill
- s3-exposure-reviewSkill
- azure-activity-investigationSkill
- azure-rbac-reviewSkill
- conditional-access-reviewSkill
- entra-audit-investigationSkill
- entra-signin-investigationSkill
- backup-assuranceSkill
- critical-service-mappingSkill
- ransomware-recoverySkill
- recovery-exerciseSkill
- cloud-exposure-reviewSkill
- cloud-incident-responseSkill
- cloud-logging-baselineSkill
- cloud-posture-assessmentSkill
- audit-evidence-packageSkill
- continuous-control-monitoringSkill
- control-mappingSkill
- control-testing-samplingSkill
- container-incidentSkill
- dockerfile-hardeningSkill
- image-scanningSkill
- runtime-detection-falcoSkill
- db-audit-loggingSkill
- db-exfiltration-investigationSkill
- db-hardeningSkill
- db-privilege-reviewSkill
- data-discoverySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Create labels and sublabels with clear names and tooltips.
- Distinctive: line 34
When classifying a dataset, ask: legal/regulatory obligations?
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Data Classification
Scheme (keep it to 3–5 levels)
| Level | Examples | Handling |
| Public | Marketing, published docs | No restrictions |
| Internal | Policies, most email | Employees only; no public sharing |
| Confidential | Customer data, contracts, source code, financials pre-release | Need-to-know; encryption in transit/at rest; external sharing only with approval/secure channels; DLP monitoring |
| Restricted | Credentials/keys, PCI cardholder data, health data, M&A, crown-jewel IP | Strict access lists, encryption with org-controlled keys, no external sharing, logging of all access, DLP blocking |
Regulated categories (GDPR special categories, PHI, PCI, export-controlled) map to the top levels with additional legal requirements.
Implementation (Microsoft Purview example)
- Create labels and sublabels with clear names and tooltips; publish label policies to users with a default label (e.g., Internal) and mandatory labelling for documents/email where culture allows.
- Protection: encryption with permissions (Restricted), content marking (headers/watermarks), container labels for Teams/SharePoint sites (privacy, external sharing).
- Auto-labelling: client-side recommendations and service-side policies using SITs (credit card numbers, national IDs, credentials), exact data match for customer records, trainable classifiers.
- Integrate with DLP policies keyed on labels.
- Measure: % of files labelled per site/workload, label downgrades (with justification), auto-label simulation results.
Decision helper
When classifying a dataset, ask: legal/regulatory obligations? impact of disclosure (customers, finances, safety)? integrity criticality? who must access it? Choose the highest applicable level; document the owner and review date.
Related skills
data-discovery, dlp-alert-triage, data-retention-review, dpia
References
- Microsoft Purview sensitivity labels: https://learn.microsoft.com/en-us/purview/sensitivity-labels
- NIST SP 800-60 (mapping information types to security categories): https://csrc.nist.gov/pubs/sp/800/60/v1/r1/final
- ISO/IEC 27001:2022 Annex A 5.12 Classification of information (standard; purchase required)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.