PREPARE
establish mission, stakeholders, roles, risk strategy, assets, architecture, common controls, authorization boundary and monitoring approach.
San Diego, CA
SOC analyst. CompTIA CySA+, CompTIA Security+, CompTIA A+, Microsoft Applied Skills (Azure networking) and CCNA coursework.
Microsoft Applied Skills: Configure secure access to your workloads using Azure networking
Five hands-on labs Abraham built and ran himself: a Wazuh SIEM, an osTicket help desk, a Wireshark capture, an Apache server on Linux, and an Active Directory domain. What you see in each section is the data those systems produced. Labs 06–09 are completed GRC study playbooks — RMF/ATO, ACAS/Nessus, DISA STIGs and eMASS/OpenRMF — written against the official references and labelled as training scenarios.
profile
Abraham has spent nearly five years keeping Department of Defense networks running in San Diego: first with the Marine Corps' 1st Network Battalion at MCRD, then at NAVWAR headquarters.
Most days that meant imaging and deploying machines, untangling Group Policy and access problems, setting people up with PIV cards and YubiKeys, and clearing vulnerability findings before they turned into audit items.
Before IT he worked in operations and compliance roles, and he holds a master's degree in piano performance from USC.
Active Secret clearance (Department of Defense), U.S. citizen
Feb 2025 to Sep 2026
Naval Information Warfare Systems Command (NAVWAR) Headquarters
Jan 2022 to Feb 2025
Marine Corps Recruit Depot (MCRD) San Diego, 1st Network Battalion
SIEM and monitoring
Vulnerability and compliance
Identity and access
Endpoint deployment
Platforms and services
Service management
One Wazuh manager plus a search indexer, with three Linux endpoints shipping their authentication and package logs to a single place where they can be alerted on.
The Wazuh single-node stack (manager + indexer) on Docker, three endpoint containers on Ubuntu 24.04, Debian 12 and Ubuntu 22.04, each running the official wazuh-agent package. Endpoints run a real sshd and rsyslog so the authentication log is genuine, not synthesised. The Windows event IDs in the reference table are the documented counterparts of these Linux events — no Windows host was part of this build.
lab1-alerts.json
Designed and deployed a containerized Wazuh SIEM, with three Linux endpoints shipping authentication, account and package logs to a central manager and indexer; diagnosed and fixed two ingestion faults along the way.
A running osTicket help desk with five support tickets worked from intake through prioritisation, troubleshooting notes, resolution and closure.
osTicket 1.18.4 on PHP 8.2 with MariaDB 11. The five tickets were opened through the real client portal form, one per requester, each with its own help topic and priority. They were then worked through osTicket’s ticket model: internal notes at triage, troubleshooting and resolution, a reply to the requester, and closure. That is the same code path the staff panel uses, and everything below is read back out of the database. A discarding sendmail stand-in let the application run without an SMTP server.
lab2-tickets.json
Deployed an osTicket help desk on Docker and worked five support tickets through their full lifecycle: intake, prioritization, troubleshooting notes, user replies and closure, including a phishing report escalated to security.
A saved packet capture of ordinary browsing, read back frame by frame: DNS lookups and their answers, a TCP three-way handshake, and a full HTTP request and response.
tshark on a scratch interface while the machine resolved four names, fetched two plain-HTTP pages and opened two TLS connections. The capture was saved as pcapng, then exported to JSON for the viewer. The pcap itself is not published — it contains the browsing of the machine that made it.
lab3-capture.json
Captured and analyzed live network traffic with Wireshark and tshark, tracing DNS resolution, the TCP three-way handshake, HTTP request/response pairs and TLS sessions across a 145-frame capture.
Ubuntu running Apache, managed entirely from the terminal: installed, started, stopped, enabled, customised, broken twice on purpose, and fixed both times.
Ubuntu under systemd, so systemctl and journalctl behave exactly as they do on a normal VM. The session was recorded live, so the timings, PIDs and error output are what the machine actually produced.
lab4-session.json
Installed and administered Apache on Ubuntu from the command line, managing the service with systemctl and journalctl, and diagnosing a configuration syntax error (AH00526) and a file-permission failure (AH00132) from the logs.
A domain with organisational units, users and security groups, plus a file share whose access is granted through group membership rather than per-user rights.
A Samba 4 domain controller provisioned as LAB.LOCAL with OUs for Staff, IT and Groups; five user accounts; HR-Team and IT-Admins security groups; and an smb.conf share restricted to @HR-Team. NT ACLs are stored in an eadb file because the container filesystem has no extended-attribute support. The access list on this page is computed from the real group membership in the directory.
lab5-directory.json
Built an Active Directory domain on a Samba AD domain controller, creating OUs, user accounts and security groups, and granting file-share access through group membership rather than per-user rights.
The seven-step Risk Management Framework from Prepare to Monitor, what an authorization package actually contains, and how everyday IT work — imaging, Active Directory, networking, patching — becomes RMF evidence.
A study playbook written against NIST SP 800-37 Rev. 2 and the NIST Authorize-step documentation, verified on 2 November 2026. It walks the full workflow, routes an authorization package from system owner to Authorizing Official, maps ordinary IT operations to control families and rehearses nine interview questions. The worked example is a fictional 100-endpoint Windows 11 fleet, and the playbook says so rather than implying a real authorization.
lab6-rmf.json
Studied and documented the NIST SP 800-37 RMF lifecycle end to end — categorization, control selection and tailoring, SSP/SAR/POA&M packaging and the AO authorization decision — with a one-week lab plan and rehearsed interview answers.
An authorized hands-on Nessus workflow from scope and credentials through validated findings, remediation tickets and rescans — plus the credentialed-scan traps interviewers probe and how scan output becomes RMF evidence.
A study playbook written against Tenable Security Center and credentialed-check documentation and NIST SP 800-37 Rev. 2, verified on 2 November 2026. It separates Nessus, Tenable Security Center and DoD ACAS, walks an eight-step authorized scan workflow, checks credentialed coverage against plugin 21745, and maps findings to RA-5, SI-2 and CM controls. The practice exercise is a two-host isolated lab, not a production scan.
lab7-acas.json
Documented an authorized Nessus scanning workflow — credentialed coverage verification, plugin-evidence validation, remediation ticketing and rescan — and mapped scan output to RMF Assess/Monitor evidence and POA&M entries.
The DISA STIG checklist workflow end to end: pick the right benchmark, run each Check Text on an authorized asset, set status from evidence, write Finding Details and Comments that survive review, and save and reimport the checklist.
A study playbook written against DISA Cyber Exchange tooling and download guidance (STIG Viewer 3.8.1, released 2026-10-02) and NIST SP 800-37 Rev. 2, verified on 2 November 2026. It distinguishes STIG, SRG, XCCDF and SCAP, walks a ten-step checklist workflow, gives three commented status templates and a version-update review routine, and closes with a ten-rule lab checklist. The comment templates are fictional and labelled as such.
lab8-stig.json
Documented the DISA STIG checklist workflow with STIG Viewer 3.8.1: benchmark import, rule-by-rule Check Text execution, evidence-backed Open/Not a Finding/Not Applicable statuses, and .cklb/.ckl export and reimport verification.
How an authorization package moves through eMASS — registration, control narratives, assessments, POA&M, review and the AO decision — and how the same workflow is practiced in an isolated OpenRMF OSS lab without pretending the lab is production.
A study playbook written against DCSA NISP guidance, the OpenRMF OSS documentation and NIST SP 800-37 Rev. 2, verified on 2 November 2026. It gives an eight-step conceptual eMASS package workflow, a seven-step OpenRMF OSS hands-on practice, a POA&M record with its evidence chain to the AO, and six interview answers including an honest response to "have you used eMASS". No production eMASS access is claimed.
lab9-emass.json
Documented the eMASS authorization-package workflow and practiced its equivalent in OpenRMF OSS — checklist and scan imports, POA&M tracking and compliance reporting — while stating the production-versus-lab boundary explicitly.
Each one links to the issuer's public record.
Microsoft
CompTIA
CompTIA
CompTIA
CompTIA
Cisco Networking Academy
Cisco Networking Academy