SSZcreate/Pentab_server / .agents/skills/cybersecurity/skills/implementing-disk-encryption-with-bitlocker
implementing-disk-encryption-with-bitlocker
VerifiedImplements full disk encryption using Microsoft BitLocker on Windows endpoints to protect data at rest from unauthorized access in case of device loss or theft. Use when deploying encryption for compliance requirements, securing mobile workstations, or implementing data protection controls across the enterprise. Activates for requests involving BitLocker encryption, disk encryption, TPM configuration, or data-at-rest protection.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 11.0 KB |
| SKILL.md | skill md | 8.7 KB |
| assets/template.md | markdown | 1.2 KB |
| references/api-reference.md | markdown | 1.6 KB |
| references/standards.md | markdown | 1.8 KB |
| references/workflows.md | markdown | 1.9 KB |
| scripts/agent.py | script | 6.3 KB |
| scripts/process.py | script | 6.2 KB |
references/workflows.md
View on GitHub# Workflows - Implementing Disk Encryption with BitLocker
## Workflow 1: Enterprise BitLocker Deployment
```
[Pre-deployment assessment]
│
├── Verify TPM 2.0 across fleet
├── Confirm UEFI/Secure Boot
├── Plan recovery key escrow (AD DS or Azure AD)
│
▼
[Configure GPO/Intune policy]
│
├── Set encryption method (XTS-AES 256)
├── Configure key protectors (TPM + PIN for laptops, TPM for desktops)
├── Enable recovery key escrow
│
▼
[Pilot deployment (test group)]
│
├── Verify encryption completes without errors
├── Test recovery key retrieval
├── Verify no boot issues
│
▼
[Production rollout (phased)]
│
▼
[Monitor encryption status via Intune/SCCM reports]
│
▼
[Verify 100% coverage, address failures]
```
## Workflow 2: BitLocker Recovery Process
```
[User locked out (BitLocker recovery screen)]
│
▼
[User provides Recovery Key ID to helpdesk]
│
▼
[Helpdesk retrieves recovery key]
│
├── AD DS: RSAT BitLocker Recovery Password Viewer
├── Azure AD: Azure Portal → Devices → BitLocker keys
├── Intune: Intune Portal → Devices → Recovery keys
│
▼
[User enters 48-digit recovery key]
│
▼
[Investigate why recovery was triggered]
│
├── BIOS/firmware update ──► [Expected, no action]
├── TPM failure ──► [Replace TPM or re-encrypt]
├── Boot configuration change ──► [Review change, re-seal TPM]
└── Potential tampering ──► [Security investigation]
```
## Workflow 3: Key Rotation
```
[Quarterly key rotation policy]
│
▼
[Generate new recovery password]
│
▼
[Backup new key to AD/Azure AD]
│
▼
[Remove old recovery password protector]
│
▼
[Verify new key works in test recovery]
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |