Environment & Gear
Uses
Hardware, development stack, and operational workflows used for designing, benchmarking, and securing distributed software systems.
Desktop & Laptop
| Primary Machine |
15.6" 2-in-1 Convertible Super AMOLED 1080p touchscreen, Intel Core i7 (11th Gen) with Intel Iris Xe Graphics, 16GB LPDDR4x RAM, 512GB NVMe SSD, 360° hinge for tablet/laptop switching. Windows 11 + Ubuntu dual-boot for cross-platform security testing. MIL-STD-810 military-grade rated. Tooling: VS Code, JetBrains, Docker Desktop, WSL2, Wireshark, Splunk, Burp Suite, S Pen for architectural diagramming. |
|---|---|
| iPad Pro Setup |
iPad Pro 13-inch (M5) — Max Configuration Apple M5 chip (10-core CPU, 10-core GPU, 16-core Neural Engine), 16GB Unified Memory, 2TB NVMe SSD storage, Ultra Retina XDR Tandem OLED display with Nano-texture glass, 5G Cellular + Wi-Fi 6E. Paired with Apple Magic Keyboard (Aluminum) and Apple Pencil Pro. Used as high-performance secondary display, portable work environment, and digital architecture canvas. |
| Mobile & Responsive Testing | Browser developer tooling, custom responsive layouts, and lightweight device emulation targets to ensure fluid accessibility across viewports (Chrome DevTools device emulation, touch-friendly viewport controls, graceful mobile layout fallbacks). |
Software Stack
| Development Suite | Python, JavaScript, Node.js, Bash, PowerShell, SQL, HTML5/CSS3, Git. Focused on rapid local iteration cycles: code, test, verify, and document. |
|---|---|
| Defensive & Audit Tools | Splunk SIEM, Suricata IDS, Wireshark packet capture, Docker containers, Burp Suite, Nmap scanner, and custom detection rule pipelines. |
Cloud & Platform Workflow
| Hybrid Environment | I use a hybrid environment where local sandboxes and cloud resources complement each other. This entails building safe configurations locally before executing against enterprise-grade telemetry and cloud deployment baselines. |
|---|---|
| Local Lab First | Docker and VM-based sandbox testing for BlueTrace, VulnShop, and software prototypes. |
| Cloud-Aware Design | AWS-style centralized logging, IAM policy audits, and detection engineering with realistic trails. |
| Documented Processes | Every lab run is captured as a clear write-up to ensure findings are reproducible. |
| Continuous Review | Threat modelling, MITRE ATT&CK mapping, and detection rule tuning are integrated into every run. |
Workflow Methodology
| 1. Plan | Define the threat scenario, pick target nodes, and select tools that match active real-world security stacks. |
|---|---|
| 2. Build | Construct the lab target, deploy dependencies, and instrument logs so that alerts and data flows can be audited. |
| 3. Test | Execute attack vectors, validate alerts telemetry, analyze logs, and tune rules to minimize false positives. |
| 4. Document | Package findings into detailed write-ups, README guides, and project repositories for verification. |