
from xalgorix627
Use sslyze to assess SSL/TLS server configurations: supported protocols, cipher suites, certificate chains, HSTS/OCSP, and common vulnerabilities like Heartblee
This skill provides a hands-on procedure for assessing SSL/TLS server security using the sslyze Python library. It describes how to enumerate supported protocol versions, evaluate cipher suite strength and ordering, validate certificate chains and SAN coverage, check HSTS and OCSP stapling, and run targeted vulnerability checks (Heartbleed, ROBOT, session renegotiation). The guidance covers scanning non-443 TLS services and explains SNI, STARTTLS, and how to corroborate findings with testssl.sh or manual openssl handshakes.
Use this skill during penetration tests, incident response, scheduled security audits, or when validating TLS configuration changes. It's appropriate when you need definitive proof (handshake success) for weak protocols or ciphers, or when auditing multiple TLS-bearing services (HTTPS, SMTP STARTTLS, IMAP, FTPS, DB TLS endpoints).
Inferred compatibility: CLI-capable agents and code-focused assistants that can run Python tooling (sslyze), such as Copilot/Codex-style or Claude-Code style agents that support running shell commands and Python scripts.
SSL/TLS security assessment skill using sslyze. No bundled scripts — purely instructional SKILL.md. The 'Most Often Missed' section is genuinely excellent, covering SNI pitfalls, STARTTLS, cipher matrix depth, and corroboration guidance. However, the four core steps are vague headers with no concrete commands, code examples, or error handling. An agent would need prior sslyze knowledge to act on this.
Strong 'Most Often Missed' section elevates this above a basic skill, but the core steps need concrete command examples and code snippets to be truly actionable. The frontmatter is well-structured with NIST CSF mappings.
Building Threat Hunt Hypothesis Framework
Framework and workflow to turn threat intelligence and telemetry into testable, falsifiable threat-hunting hypotheses for proactive detection.
Ransomware-Resilient Backup Strategy
Designs and documents a ransomware-resilient backup architecture (3-2-1-1-0), immutability, credential isolation and automated restore testing aligned to RPO/RT
Pentesting rsync (port 873)
Procedures and checks to enumerate and exploit rsync daemon modules (port 873), detect unauthenticated shares, brute-force auth, and safely verify read/write ex
Configuring Identity-Aware Proxy (IAP) for Google Cloud
Step-by-step guide to secure Google Cloud services (Compute, App Engine, Cloud Run, GKE) with Identity-Aware Proxy, access levels, and programmatic service-acco
Deception-Based Detection with Canarytoken
Create, deploy, and monitor Thinkst Canary Tokens (web, DNS, document, AWS key) to detect lateral movement and credential misuse.