blue-team-root
Fundamental blue team skills for detecting threats, responding to incidents, and defending systems in cybersecurity.
What this skill does
# blue-team-root
## Purpose
This skill provides core blue-team functionalities for cybersecurity, enabling threat detection, incident response, and system defense. It integrates with tools like intrusion detection systems and logging frameworks to protect against cyber threats.
## When to Use
Use this skill when monitoring network traffic for anomalies, responding to security incidents, or hardening systems. Apply it in real-time threat detection scenarios, such as during a suspected breach, or for proactive defense in environments like cloud infrastructures or on-premise servers.
## Key Capabilities
- **Threat Detection**: Scan networks using tools like Snort; example: detect intrusions by analyzing packet captures with `snort -A console -q -c /etc/snort/snort.conf`.
- **Incident Response**: Automate containment via scripts that isolate affected hosts; e.g., use a Python snippet to block IP: `import subprocess; subprocess.run(['iptables', '-A', 'INPUT', '-s', '192.168.1.1', '-j', 'DROP'])`.
- **System Defense**: Configure firewalls and monitoring; set up OSSEC for real-time alerting with config like `<global><email_notification>yes</email_notification></global>` in ossec.conf.
- **Log Analysis**: Parse logs with ELK stack; query Elasticsearch endpoint `/logs/_search` with JSON payload `{"query": {"match": {"message": "suspicious login"}}}`.
- **Vulnerability Scanning**: Run Nessus scans via API; endpoint `POST /scans` requires JSON body like `{"policy_id": 1, "targets": ["192.168.1.0/24"]}`.
## Usage Patterns
Invoke this skill in OpenClaw by calling the skill ID "blue-team-root" with specific parameters. For example, to detect threats, use: `openclaw execute blue-team-root --action detect --target 192.168.1.0/24`. In code, integrate via OpenClaw SDK: `from openclaw import Skill; skill = Skill('blue-team-root'); result = skill.run(action='respond', incident_id='INC001')`. Always set auth with environment variable `$OPENCLAW_API_KEY` before execution. Chain with other skills by piping outputs, e.g., detect then respond: `openclaw execute blue-team-root --action detect | openclaw execute blue-team-root --action respond`.
## Common Commands/API
- **CLI Commands**: Use `openclaw blue-team-root detect --flags -i interface -t timeout` to start network monitoring; flags include `-i` for interface and `-t` for scan timeout in seconds.
- **API Endpoints**: Access via HTTP POST to `https://api.openclaw.ai/blue-team/detect` with body `{"target": "192.168.1.0/24", "auth": "$OPENCLAW_API_KEY"}`; response includes JSON like `{"status": "detected", "threats": ["SQL injection"]}`.
- **Code Snippets**: For incident response, use: `response = requests.post('https://api.openclaw.ai/blue-team/respond', json={"incident": "INC001", "action": "isolate"}); print(response.json()['status'])`. Another: `os.system('snort -c /etc/snort.conf -A fast > detection.log')` to log detections.
- **Config Formats**: Use YAML for configurations, e.g., `detection: { threshold: 5, rules: ['rule1', 'rule2'] }`; load in Python with `import yaml; config = yaml.safe_load(open('config.yaml'))`.
## Integration Notes
Integrate with external tools by exporting results to SIEM systems like Splunk via webhook: `openclaw blue-team-root --action export --format json --url https://splunk.example.com/api`. For authentication, always use `$OPENCLAW_API_KEY` in headers, e.g., `headers = {'Authorization': f'Bearer {os.environ.get("OPENCLAW_API_KEY")}'} in Python requests. Combine with red-team skills for simulations; pipe output directly, e.g., `openclaw execute red-team-sim | openclaw execute blue-team-root --action detect`. Ensure compatibility by matching API versions, like OpenClaw v2.0.
## Error Handling
Handle errors by checking API responses for status codes; if 401, retry with refreshed `$OPENCLAW_API_KEY`. For CLI, use try-except in scripts: `try: subprocess.run(['snort', '-c', 'config'], check=True) except subprocess.CalledProcessError as e: print(f"Error: {e.returncode} - {e.output}")`. Common issues include network timeouts; implement retries with exponential backoff, e.g., `for attempt in range(3): try: requests.get(url) except requests.exceptions.Timeout: time.sleep(2**attempt)`. Log all errors to a file for auditing, using Python's logging: `import logging; logging.basicConfig(filename='blue-team.log', level=logging.ERROR)`.
## Concrete Usage Examples
1. **Threat Detection Example**: To detect potential threats on a network, run: `openclaw execute blue-team-root --action detect --target 192.168.1.0/24 --auth $OPENCLAW_API_KEY`. This scans the subnet and returns anomalies; follow up by parsing the JSON output to alert on high-severity items.
2. **Incident Response Example**: For an active incident, use: `openclaw execute blue-team-root --action respond --incident_id INC002 --steps isolate,notify`. This isolates the affected host and sends notifications; in code, verify with `if response['status'] == 'success': print('Incident contained')`.
## Graph Relationships
- **Parent Cluster**: Connected to "blue-team" cluster for broader cybersecurity operations.
- **Related Skills**: Links to "incident-response" (ID: blue-team-ir) for advanced response tactics; and "threat-intelligence" (ID: blue-team-ti) for intelligence gathering.
- **Downstream Dependencies**: Requires "logging-core" skill for log access; outputs to "alerting-system" for notifications.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.