Cisco Certified in Cybersecurity
Foundational security operations credential: threats, vulnerabilities, network defense, and incident handling.
THREAT ANALYSIS · CISCO CERTIFIED · (ISC)² CANDIDATE · BTJA
I build the tools defenders actually use: exposure assessment, STIG-style compliance auditing, and threat-intel pipelines mapped to NIST 800-53 and MITRE ATT&CK. B.S. Cybersecurity (Security Threat & Analysis), Iona University. End goal: taking cybercrime off the board.
This terminal is real. Try help, trace, scan, mission, or hire. Tab completes.
I'm a threat analyst and security toolsmith from New York's Hudson Valley, starting my B.S. in Cybersecurity at Iona University this fall with a concentration in Security Threat & Analysis. I didn't wait for the degree to start building: the tooling on this page already exists, runs, and is documented.
My foundation is defensive: Cisco's cybersecurity certification, official (ISC)² Candidate status, and the complete BTJA blue-team pathway. On top of that I've stacked serious applied-AI training, Anthropic certifications covering the Claude API, Model Context Protocol, agent architectures, and enterprise deployment on AWS Bedrock and Google Cloud Vertex AI. That combination is why I can ship tools at this pace.
Outside the SOC, I compete internationally on the Great Highland Bagpipe: 1st place, North American Championship (Youth, 2025) and 8th at the World Championship in Glasgow (2024). Ten years of competition taught me what incident response also demands: disciplined practice and precision when it counts.
Every certificate below is verifiable: core credentials via Credly, Anthropic certificates as signed PDFs you can open right here.
Foundational security operations credential: threats, vulnerabilities, network defense, and incident handling.
Official candidate status with the organization behind the CISSP and CC certifications.
Complete BTJA pathway: SOC fundamentals, log analysis, network traffic analysis, and defensive operations. Certificate (PDF) ↗
Custom assessment tooling, packaged together as the Security Audit & Verification Suite on GitHub.
GAMECHANGER-inspired semantic search + cited QA over DoD policy
Built against the CDAO analytic-tools ecosystem (GAMECHANGER, Advana, JATIC). Every version ships an adversarial self-critique: assume it's broken until proven otherwise.
A testable detection engine: Sigma-style rules over event logs, mapped to MITRE ATT&CK
docker run -p 8080 fails the buildDetection engineering treated like code: rules with tests and a measurable quality bar. Because a rule that cries wolf is worse than no rule.
Authorized network exposure assessment
Local baseline & compliance auditor
Threat intelligence pipeline
Threat-intel operations platform
Techniques my tooling detects, audits against, or enriches; hover any lit cell. Honest coverage, not a checkbox wall. An analyst who maps his own work to ATT&CK is an analyst who understands the framework.
Not a simulation. This board fetches current threat data on the edge from CISA and abuse.ch, the same feeds a working SOC uses. It refreshes every 30 minutes.
Loading current CVEs…
Loading live C2 servers…
Loading recent IOCs…
CISA KEV lists what's already weaponized. This board looks one step upstream: the newest CVEs from NVD, scored by EPSS — the probability a flaw gets exploited within 30 days — and filtered to the ones not yet in KEV. High EPSS + high CVSS + no KEV listing is the patch-it-now quadrant. Live, sourced, refreshed every 30 minutes.
Ranking newest CVEs by exploitation probability…
Ranking = EPSS probability first, then CVSS severity, then recency. EPSS via FIRST.org; scores shift daily as exploitation signal accrues. This is public-data analysis, not a claim of private discovery.
Exploit search engines answer “does an exploit exist for this CVE?” — a question whose answer is eventually always yes, which makes it useless for ordering a patch queue. The question that does reorder one is how long after disclosure exploitation actually begins. This board measures exactly that, across the entire CISA KEV corpus: KEV dateAdded − NVD published, for every catalogued vulnerability. Both sources are authoritative, so every figure here is independently reproducible.
Loading…
Loading…
CISA seeded KEV in November 2021 with a large historical backfill, so 2021–2022 entries measure cataloguing latency, not weaponization speed — their medians run to years and pooling them would be a measurement error. Every headline figure above is computed on the 2023-onward subset; the chart shows all years so you can see the break for yourself. Two further limits, stated rather than buried: dateAdded records when CISA confirmed exploitation, which lags first exploitation by an unknown margin, so these are an upper bound — the real runway is shorter, never longer. And KEV is a selected sample of what CISA tracks for federal risk, not a census of everything exploited in the wild.
Ransomware crews run victim-shaming portals as Tor hidden services. Organizations get posted there hours to days before any press coverage — which makes leak-site monitoring one of the earliest public signals in all of threat intelligence. This board reduces that feed to what actually matters: which crews are operating, at what tempo, and who they're selecting. Aggregated via ransomware.live.
Loading…
Loading…
Loading…
This board shows aggregate counts only. I deliberately withhold victim organization names and every .onion address, and the endpoint never emits them to the browser. Victims of extortion are crime victims — republishing their names adds pressure and produces no analytic value that the trend data doesn't already carry. Naming targets is what the crews want; counting them is what defenders need.
You cannot defend a technique you don't understand offensively. Each card below is a tradecraft pattern dominating 2026 intrusions, paired with the telemetry that actually detects it. No exploit code — the deliverable of red-team knowledge on a blue team is detection logic.
The dominant modern intrusion drops no payload at all. Operators buy or phish credentials, authenticate through the front door, and inherit the user's trust. CrowdStrike put 82% of 2025 detections in the malware-free category. There is no hash to blocklist and no file to quarantine.
Identity telemetry becomes the primary sensor. Alert on first-seen ASN or device for a principal, impossible-travel deltas, interactive logon by a service account, and MFA-fatigue push patterns. The signal is deviation from that identity's baseline, not badness in a file.
Execution is proxied through Microsoft-signed binaries already present and trusted: rundll32, regsvr32, mshta, certutil, msbuild. Blocklisting them breaks Windows, so they survive allowlisting by construction.
Baseline legitimate parent-child lineage, then alert on the anomaly: rundll32 with no command line, Office spawning a script host, certutil invoked with -urlcache or -decode. My Detect Lab ships a tested rule for exactly this certutil transfer pattern, gated in CI against false positives.
Before acting, capable operators degrade visibility: patching ETW providers in-process, removing userland hooks, or stopping the agent outright. The intrusion continues in a gap where nothing is being written down.
Monitor telemetry integrity, and treat absence of signal as signal. A host that stops heartbeating, an ETW provider that goes quiet, or a sensor version that silently rolls back should page someone. Enable tamper protection so the disable attempt itself is the alert.
VPN concentrators, firewalls, and file-transfer appliances sit internet-facing and cannot run an EDR agent. Crews operationalize n-days within days of disclosure and land in the one place the security stack cannot see.
Ship appliance syslog to the SIEM as a first-class source, diff running configs on a schedule, and alert on any outbound session originating from a management plane that should only ever receive. My Emerging Exposure board exists to shorten the window on exactly this class of CVE.
Sandbox and VM evasion was 2026's fastest-growing technique, climbing to the top five. Payloads fingerprint the host — domain membership, uptime, user artifacts, CPU count — and simply exit clean inside analysis environments.
Detonate in environments with realistic decoy artifacts and aged profiles, and extend observation past timer-based delays. Treat early clean exit as suspicious in itself: a sample that checks the environment and quits has told you something about its intent.
Encryption for impact (T1486) fell roughly 38% relative in 2026. Crews increasingly steal and threaten without ever encrypting: it is quieter, keeps the host alive for continued access, and still monetizes. The leak-site tempo on the board above is this shift, measured.
The detonation-time trigger never fires, so detection moves left to data movement. Baseline egress volume per host and per identity, alert on archive utilities and rclone-class transfer tooling, and watch for bulk reads against file shares that a given account has never touched before.
Technique IDs are MITRE ATT&CK Enterprise. Prevalence figures reflect published 2025–2026 industry telemetry from CrowdStrike, Red Canary, and Picus; they are cited as reported, not independently measured by me.
Reading about SIEM, Active Directory, and mail security isn't the same as running them. These are infrastructure-as-code labs I stand up, attack, and then hunt in the logs — the full detection loop on infrastructure I control. Everything here is real, runnable code; each card links the build you can clone and run yourself.
Elasticsearch + Kibana + Filebeat, with detections as code
The point isn't a dashboard — it's the analyst loop end to end, on infrastructure I own and can rebuild in minutes.
A domain you provision from code, attack, then catch in the logs
lab.local) and a domain-joined Win10 workstationYou can't reliably detect what you've never watched happen. This lab is where I watch it happen — inside my own domain, on accounts built for the purpose.
Self-hosted mail stack for phishing and header analysis
Received:-chain and Authentication-Results triage — the core of phishing analysisReal Exchange needs Windows Server and licensing; this teaches the same defensive surface on a laptop, with the Exchange upgrade path written down.
Pipelines that fail the build on a security regression
git pushNot a lab I spun up for show — this is how the projects in FILE 06 are actually built. The evidence is in the pipelines.
Threat-intelligence work I measured myself, with the collection method published so you can reproduce or dispute it, alongside the coordinated-disclosure process I hold myself to.
I pulled the 100 most recent ransomware leak-site postings and counted what was in them. Five crews held 56% of activity, and 58% carried infostealer linkage — evidence that most extortion now starts with bought credentials, not exploited software. Includes stated collection limits and the SOC detection response.
Read the analysis ↗ POLICYMy VDP for anyone testing this site, and the five-step process I follow when I find something in someone else's: authorization first, minimum necessary proof, private report, coordinated timeline, publish after the fix.
Read the policy ↗When authorized research of mine results in a CVE, the advisory and vendor acknowledgment get listed here. Until then this stays empty on purpose. I'd rather show you a blank slot than pad it.
Every card below is a working deployment or a live GitHub repo, not mockups. Open a demo in the theater or jump straight to source.
Syncing repos…
Local-first password manager: AES-256 encryption, secure authentication, cryptographically strong generation, zero cloud dependency by design.
License & permit tracker with automated email reminders at 30/7/1 days before expiry. User auth, tiered free/pro plans, Stripe billing, cron-secured task endpoints.
Open-government dashboard on U.S. Census ACS data. Async httpx ingestion, TTL caching, Chart.js visualization, WCAG-conscious accessibility, with GitLab CI enforcing SAST and secret detection before every merge.
Hand-built with vanilla HTML/CSS/JS on Cloudflare Pages, live threat-feed ticker and AI assistant run as serverless Pages Functions, shipped with hardened security headers.
AI business-assistant landing page with a live Workers AI demo and contact capture through Cloudflare Pages Functions.
Dental-practice automation landing page: ROI calculator, workflow template previews, and lead capture, optimized for Cloudflare Pages.
Python scraper that extracts structured reference material and generates clean, formatted PDF cheat sheets.
1st place, North American Championship (Youth, Aug 2025). 8th place, World Championship, Glasgow (Aug 2024). Multiple piping scholarships, 2023–2026.
Customer service, transactions, and holiday-rush operations in a high-volume retail environment.
Meal service for food-insecure neighbors; assisted elderly clients with medical equipment rentals at Poughkeepsie Reformed Church.
Guest safety and high-volume operations during peak summer season.
Hover (or tab to) any redaction to declassify.
PRIMARY OBJECTIVE: Take cybercrime off the board, ransomware crews, fraud networks, and the infrastructure they run on.
THEATER OF INTEREST: Overseas operations, Middle East posting, where cyber and national security intersect hardest.
TARGET TRACKS: FBI Cyber Division, Honors Internship · NSA student programs & Codebreaker Challenge · CIA digital-targeting pathways · CISA / DHS cyber.
CURRENT PHASE: Building the record that opens those doors, verified certifications, shipped defensive tooling, a Security Threat & Analysis degree, and the public body of work you're reading right now.
— RODRIGUEZ, S.W. APPROVED FOR RELEASE
Security roles, collaborations, or hard questions. I respond fast.
An AI briefed on this dossier. Ask it anything about my skills, tools, or availability.