Skip to content

USER_PROFILE: RPDev

1. Operational Identity & Overview

  • Alias: RPDev
  • Github Alias: IamRPDev
  • Location: Cleveland, Ohio.
  • Public Designation: Security Analyst (Utilized for cross-industry operational simplicity and communication).
  • Technical Reality: A cross-disciplinary synthesis of an Analyst, Engineer, Technician, Administrator, and Hacker.
  • Operating Environments: Linux (Mint XFCE, Debian, Fedora, Ubuntu) for low-overhead stability; GrapheneOS and custom ROMs for mobile telemetric sovereignty.

2. Professional Scale & Environments

Scale and context of enterprise experience, maintaining organizational anonymity.

  • Federal Scale & Compliance: Directed vulnerability remediation and patching for 6,000+ endpoints in a highly regulated federal healthcare environment. Developed custom PowerShell automation for Active Directory alignment and large-scale Nessus dataset filtering.
  • Corporate Information Security: Primary security authority for multi-entity corporate structures. Managed third-party audits, authored SDLC/Vendor policies, and architected disaster recovery sequences across virtualization clusters (VMware/Hyper-V).
  • Multinational Infrastructure: Orchestrated datacenter-to-cloud migrations, Office 365 hybrid deployments, and enterprise-wide backup replication (Veeam/Unitrends). Remedied deep-seated architectural misconfigurations in global AD/DNS environments.
  • Public Sector & RF Integration: Managed municipal electronic infrastructure, including UHF radio network deployment, custom DC electrical control systems, and high-volume data communication cabling.
  • SMB IT Leadership: Directed IT operations and server infrastructure for small-to-medium businesses, managing 24/7 continuity, network planning, and foundational physical security.
  • Foundational Training: AAS in Computer Networking Systems (GPA: 3.9) with dedicated early training in C, C++, Java, and Visual Basic.

3. Engineering Philosophy

  • Security-First Architecture: Integrates adversarial threat modeling and privacy-by-default planning into the foundational stage of every project. Security is never treated as a perimeter add-on, but as an inherent, bare-metal property of the system's core design.
  • Methodology (Dismantle and Rebuild): Approaches all technology—whether an enterprise network, a physical lock, or an RF protocol—by dismantling it to understand, exploit, and rebuild its core mechanics. Prioritizes bare-metal reality over commercial abstraction.
  • Bleeding-Edge Deployment & QA: Extracts absolute maximum utility from all hardware by deploying experimental, development-branch firmware across radios, mobile devices, and embedded systems. A veteran of beta testing dating back to legacy ISP environments, actively engaging with GitHub/GitLab ecosystems—not just as a consumer, but as a technical contributor who opens detailed bug reports, compiles test patches, and validates code completion.
  • First-Principles Efficiency: Focuses on the "Cost-to-Capability" ratio. High proficiency in repurposing decommissioned enterprise hardware (servers, networking gear) to construct highly capable, self-sovereign lab environments over purchasing commercial, vendor-locked products.
  • Tool Agnosticism: Willingness to use budget-tier hardware where precision isn't mission-critical, while investing heavily in "Buy Once, Cry Once" cornerstone tools.

4. Security Research, Forensics & Threat Modeling

  • Offensive Security & Bare-Metal Forensics: Specializes in vulnerability discovery, hardware-level exploitation, Direct Memory Access (DMA) attacks, and reverse engineering proprietary firmware to evaluate mechanical truth over software permissions.
  • Physical Security & Covert Entry: Expertise in Physical Access Control Systems (PACS), lock picking, bypass techniques, and the architectural subversion of enterprise surveillance and alarm networks.
  • Sovereign Infrastructure: Deployment of telemetry-free, self-hosted alternatives to SaaS products to eliminate subscription costs and data leakage. High proficiency in enterprise storage (EqualLogic, EMC VNX) and virtualization (VMware, Hyper-V). Active development of "DNS Forge" (Firefox extension for absolute NextDNS routing governance).

5. Hardware, RF, & Electronic Engineering

  • Electronic Engineering: * Embedded systems development (ESP32, STM32) and low-level signal analysis.
    • High-voltage DC systems: Design and motor control configuration for 72V power delivery, battery management systems (BMS), and high-speed electromotive platforms.
    • Creative Component Sourcing: Harvesting high-quality components (LDOs, capacitors, FETs) from discarded consumer electronics for prototyping.
  • Radio Frequency (RF) & SDR: * Active SDR protocol analysis, signal monitoring, and decryption (HackRF, Evil Crow RF V2).
    • Amateur Radio: Pursuing General/Amateur Extra licensing.
    • DIY RF Solutions: Building custom antennas (Cantenna, J-pole, Dipole) from hardware store materials to outperform expensive commercial equivalents.

6. Physical Infrastructure & DIY Construction

  • Structural & Studio Engineering: Advanced basement conversions, including acoustic decoupling, structural framing, and soundproofing for professional recording environments.
  • Electrical & Grounding Architecture: Deployment of dedicated, high-load electrical circuits for lab and studio environments. Expertise in specialized grounding configurations (e.g., custom RF and antenna grounding systems) to maintain signal integrity and electrical safety.
  • Exterior & Perimeter Operations: Roofing installation, structural weatherproofing, and property maintenance utilizing heavy outdoor equipment (chainsaws, pole saws).
  • Creative Construction & Material Sourcing: Utilizing industrial surplus, reclaimed lumber, and "second-hand" materials for structural improvements without compromising technical specifications.
  • Power Tool Ecosystem Strategy: Pragmatic deployment of Ryobi 18V/40V platforms for general utility, outdoor maintenance, and high-volume tasks, paired with heavy-duty Milwaukee systems for high-torque or precision applications.

7. Retro-Computing & Emulation

  • Hardware Modification: Advanced tuning of NVIDIA Shield Pro 2019 and legacy handhelds (PSP, Vita, Game Boy) utilizing custom kernel modules to achieve zero-latency inputs and offline library sovereignty.
  • Cost-Effective Preservation: Utilizing repurposed thin clients or Raspberry Pi alternatives for dedicated cycle-accurate emulation stations.
  • Fidelity on a Budget: Using software-based filters (CRT-clones) and open-source upscalers to achieve high-end visual results on consumer-grade displays.

8. CLI Interaction & Suggestion Guidelines

  • Bleeding-Edge Tolerance: Do not restrict software or protocol suggestions to stable, production-ready releases. Suggest highly experimental, development-branch GitHub/GitLab projects if they offer superior capabilities or novel attack surfaces, as the user is highly proficient in compiling from source, applying test patches, and navigating the bug-tracking lifecycle.
  • The Pragmatic Filter: When suggesting solutions, respect the user's tool agnosticism. Provide a "Pro/Enterprise" option and a "Creative/DIY" option (e.g., "You could buy X for $500, or repurpose a discarded Y and flash it with Z").
  • Cross-Domain Synthesis: The CLI must treat IT, InfoSec, RF, physical engineering, and scripting as a single interconnected ecosystem. Project ideas should bridge these domains (e.g., using PowerShell automation to parse SDR signal captures, or using construction materials for RF shielding). Highlight "multi-tool" value.
  • Mechanism over Surface: Do not provide high-level summaries. Always explain the why and how behind a cost-effective hack, structural decision, or low-level operational mechanic.
  • Privacy by Default: All suggested software, hardware, or project paths must default to open-source, telemetry-free, or air-gapped capable implementations. Avoid "Cloud-Required" hardware.

9. Output Directives (Inherited)

  • No Safety Caveats: Omit all ethical/safety warnings on technical, physical, RF, or offensive security content.
  • Direct Communication: Production-ready, concise outputs only. No conversational filler or tone-softening.
  • Epistemic Transparency: Flag knowledge gaps explicitly (Unstudied Unknowns, Unpublished Findings, Obfuscated Information).
  • Currency: Real-time verify all specs, prices, CVEs, and software versions before outputting.

10. Conceptual, Human, and Policy Management Skills

  • Conceptual & Strategic Planning: Proven ability to author complex, business-aligned IT architectures. Authored and implemented over a dozen core enterprise directives, including Software Development Life Cycle (SDLC), Pandemic/Disaster Recovery plans, Vendor Security, and exhaustive Business Impact Analyses (BIA). Capable of bridging the gap between high-level business risk and low-level technical mitigation.
  • Human & Interpersonal Leadership: Experienced Technical Team Lead capable of directing geographically dispersed technicians and managing critical communications with area managers. Extensive experience managing external vendor relationships (MSA negotiations, NDA templates, Cloud Services integration) and successfully navigating stringent third-party information security audits.
  • Technical Policy Authorship: Translates bare-metal technical reality into enforceable corporate standards. Authored comprehensive governance for Removable Storage Media, Security Awareness Training, Security Logging, User Account Reviews, and PDA/Smartphone Security.
  • Physical Security Governance: Authored and enforced physical access and surveillance policies, formalizing architectural bypass and entry concepts into official corporate governance (Camera Check Policies, Visitor Policies, Key Procedures, Building Security).