mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-07-22 20:51:01 +03:00
mukul975
cb8d79e068
- Add validated mitre_attack frontmatter to all 754 skills (286 distinct techniques), verified against MITRE ATT&CK v19.1 via the official mitreattack-python library: 0 revoked, deprecated, or invalid IDs - Curate precise per-skill technique IDs for forensics, malware-analysis, threat-intel, and red-team skills (e.g. DCSync -> T1003.006, Kerberoasting -> T1558.003, Pass-the-Ticket -> T1550.003) - Reconcile v19.1 tactic restructuring: Defense Evasion split into Stealth (TA0005) and Defense Impairment (TA0112); revoked T1562.* family and T1070.001/.002 remapped to active equivalents (T1685.*) - Normalize word-split tags across 35 skills (remove filename-derived stopword tags, add semantic cybersecurity tags) - Add api-reference.md for 3 skills that were missing it - Update README ATT&CK section with accurate v19.1 tactic distribution
72 lines
2.3 KiB
Markdown
72 lines
2.3 KiB
Markdown
---
|
|
name: implementing-log-integrity-with-blockchain
|
|
description: Build an append-only log integrity chain using SHA-256 hash chaining
|
|
for tamper detection. Each log entry is hashed with the previous entry's hash to
|
|
create a blockchain-like structure where modifying any entry invalidates all subsequent
|
|
hashes. Implements log ingestion, chain verification, tamper detection with pinpoint
|
|
identification, and periodic checkpoint anchoring to external timestamping services.
|
|
domain: cybersecurity
|
|
subdomain: security-operations
|
|
tags:
|
|
- log-integrity
|
|
- tamper-detection
|
|
- hash-chaining
|
|
- sha-256
|
|
- audit-logging
|
|
- security-operations
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
nist_csf:
|
|
- DE.CM-01
|
|
- RS.MA-01
|
|
- GV.OV-01
|
|
- DE.AE-02
|
|
mitre_attack:
|
|
- T1078
|
|
- T1190
|
|
- T1059
|
|
---
|
|
|
|
|
|
# Implementing Log Integrity with Blockchain
|
|
|
|
|
|
## When to Use
|
|
|
|
- When deploying or configuring implementing log integrity with blockchain capabilities in your environment
|
|
- When establishing security controls aligned to compliance requirements
|
|
- When building or improving security architecture for this domain
|
|
- When conducting security assessments that require this implementation
|
|
|
|
## Prerequisites
|
|
|
|
- Familiarity with security operations concepts and tools
|
|
- Access to a test or lab environment for safe execution
|
|
- Python 3.8+ with required dependencies installed
|
|
- Appropriate authorization for any testing activities
|
|
|
|
## Instructions
|
|
|
|
1. Install dependencies: `pip install requests`
|
|
2. Ingest log entries from syslog, JSON, or plain text files.
|
|
3. For each entry, compute SHA-256 hash of: previous_hash + timestamp + log_content.
|
|
4. Store the chain as a JSON ledger with entry index, timestamp, content hash, previous hash, and chain hash.
|
|
5. Verify chain integrity by recomputing all hashes and detecting breaks.
|
|
6. Optionally anchor checkpoint hashes to an external timestamping service.
|
|
|
|
```bash
|
|
python scripts/agent.py --log-file /var/log/syslog --chain-file log_chain.json --verify --output integrity_report.json
|
|
```
|
|
|
|
## Examples
|
|
|
|
### Chain Entry Structure
|
|
```json
|
|
{"index": 42, "timestamp": "2024-01-15T10:30:00Z", "content_hash": "a1b2c3...",
|
|
"prev_hash": "d4e5f6...", "chain_hash": "SHA256(prev_hash + timestamp + content_hash)"}
|
|
```
|
|
|
|
### Tamper Detection
|
|
If entry 42 is modified, chain_hash[42] will not match SHA256(chain_hash[41] + ...), and all entries from 42 onward will be flagged as invalid.
|