Skip to content
View SecByAlii's full-sized avatar
πŸ€ͺ
Always Here
πŸ€ͺ
Always Here

Block or report SecByAlii

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
SecByAlii/README.md

πŸ‘‹ About me

I'm a full-time data analyst working toward a B.S. in cybersecurity β€” I learn by taking things apart to see how they break, then figuring out how to catch it next time.

  • πŸš€ The goal: securing space operations. The systems and ground infrastructure behind the missions β€” at an organization like NASA or Lockheed Martin. That's what I'm building toward, one project (and a NASA internship) at a time.
  • πŸ”Ž Investigated a breach, start to finish β€” ran a credential-based intrusion on my own lab, then worked it like a real incident: reconstructed the attacker's every move from the logs, found root cause, and wrote the client report. DFIR is the work I want to do.
  • πŸ”­ Built a home-lab SOC β€” 15 attacker techniques across Linux and Windows, detected in Splunk, MITRE ATT&CK-mapped and rolled into scored incidents.
  • πŸ₯ Wrote a full HIPAA Security Rule risk assessment for a (fictional) eye practice: 20 risks scored NIST-style, a patient-safety risk most assessments miss, and a fix plan where the first 30 days cost about $0. Seven years inside eye clinics means I know where patient data actually leaks.
  • 🌱 Working through my cybersecurity coursework, one lab at a time
  • πŸ’» Day job: turning messy data into decisions people actually act on
  • πŸ› Also run the tech side of a small woodworking business β€” because apparently one skillset was never enough

πŸ› οΈ Featured builds

Project What it is
perikrone Security tooling (SSPM) β€” an agentless, read-only Microsoft 365 identity-posture auditor that flags misconfigurations (missing MFA, over-privileged admins, stale/guest accounts) and maps each finding to its HIPAA Security Rule control. Live scan dashboard, guided remediation, and posture-over-time trending. Pure Python, no dependencies.
incident-report-01 DFIR β€” a full investigation of a simulated Windows breach: timeline reconstruction, forensic artifacts, root-cause analysis, and a client-ready report, backed by Splunk evidence. The investigation side of the home-lab-soc detections.
home-lab-soc Detection lab β€” 15 attacker techniques across Linux and Windows hosts, a tuned Splunk detection for each (MITRE ATT&CK-mapped, with documented false positives), a session-level correlation layer, and a dashboard. Writeup.
hipaa-risk-assessment GRC: a HIPAA Security Rule risk analysis for a 3-provider eye practice. Asset inventory, 20 threat/vulnerability pairs, a NIST SP 800-30 risk register, a phased remediation plan, and a one-page executive summary.
landscaping-crm-prototype Proof-of-concept CRM β€” customer management, crew scheduling, bidding, invoicing, automated review requests

Pinned Loading

  1. hipaa-risk-assessment hipaa-risk-assessment Public

    HIPAA Security Rule risk analysis for a fictional 3-provider eye practice: asset inventory, threats, NIST SP 800-30 risk register, phased remediation plan, executive summary.

  2. home-lab-soc home-lab-soc Public

    Detection lab: 15 attacker techniques across Linux and Windows, simulated and detected in Splunk, MITRE ATT&CK-mapped, correlated into scored incidents.

  3. landscaping-crm-prototype landscaping-crm-prototype Public

    Prototype CRM for a landscaping business β€” customer management, crew scheduling, bidding, invoicing, and automated review requests. Built as a proof-of-concept before a production build.

    HTML

  4. incident-report-01 incident-report-01 Public

    DFIR investigation of a simulated Windows breach: brute-force entry, persistence, blocked LSASS dump, log clearing β€” reconstructed from Splunk. Full incident response, scenario to client report.