{"data":{"projects":{"edges":[{"node":{"frontmatter":{"title":"CNIT 32300 Basic Cyberforensics","description":"A digital forensics course where I studied evidence handling, file systems, storage behavior, encryption, investigation methods, and simulated case analysis.","tech":["Digital Forensics","File Systems","Evidence Analysis","Encryption"],"github":"","external":"","icon":"FingerprintPattern","date":"2025-12-01","order":10,"highlightOrder":11},"excerpt":"A Purdue CIT cyberforensics course where I studied digital evidence, file systems, storage behavior, caching, encryption, and investigation methods through…","html":"<p>A Purdue CIT cyberforensics course where I studied digital evidence, file systems, storage behavior, caching, encryption, and investigation methods through simulated case work.</p>\n<h3>What this was</h3>\n<p>CNIT 32300 introduced the fundamentals of cyberforensics and cyber-crime scene analysis. The course focused on how investigators identify, preserve, interpret, and explain digital evidence while considering legal, regulatory, and professional standards.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Studied how storage behavior, caching, file types, metadata, and encryption can affect digital investigations.</li>\n<li>Practiced reading evidence left behind in simulated forensic scenarios.</li>\n<li>Connected technical findings to timelines, user behavior, motive, and case reasoning.</li>\n<li>Learned how structured methodology helps investigators avoid assumptions and support conclusions with evidence.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course helped me think more like an investigator. I learned that cyberforensics is not only about finding files; it is about explaining what the evidence means, how reliable it is, and how it fits into a broader incident or case narrative.</p>"}},{"node":{"frontmatter":{"title":"CNIT 34400 Network Engineering Fundamentals","description":"A network engineering course where I worked with switching, routing, VLANs, ACLs, DHCP, subnetting, wireless access points, and firewall concepts.","tech":["Routing and Switching","VLANs","ACLs","Subnetting"],"github":"","external":"","icon":"Network","date":"2025-05-01","order":9,"highlightOrder":9},"excerpt":"A Purdue CIT network engineering course where I worked with enterprise networking fundamentals, including switches, routers, wireless access points…","html":"<p>A Purdue CIT network engineering course where I worked with enterprise networking fundamentals, including switches, routers, wireless access points, firewalls, VLANs, ACLs, DHCP, and subnetting.</p>\n<h3>What this was</h3>\n<p>CNIT 34400 built on earlier systems and infrastructure coursework by moving deeper into network design, implementation, and troubleshooting. The course focused on how wired and wireless networks are structured, how network devices interact, and how addressing decisions affect real environments.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Practiced core network engineering concepts across switching, routing, wireless, and firewall scenarios.</li>\n<li>Studied VLANs, DHCP, ACLs, spanning tree, subnetting, and network addressing.</li>\n<li>Worked through labs, assignments, and troubleshooting exercises based on enterprise-style network hardware concepts.</li>\n<li>Used command line tools to inspect, configure, and reason through network behavior.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course helped me understand networking as the foundation that everything else depends on. It strengthened how I think about traffic flow, segmentation, device roles, address planning, and troubleshooting in enterprise-style environments.</p>"}},{"node":{"frontmatter":{"title":"CNIT 51100 Foundations in Homeland Security Studies","description":"A homeland security course where I studied risk assessment, physical security, emergency management, crisis response, and infrastructure protection.","tech":["Risk Assessment","Physical Security","Emergency Management","Crisis Response"],"github":"","external":"","icon":"ShieldLock","date":"2025-12-01","order":11,"highlightOrder":12},"excerpt":"A Purdue CIT homeland security course where I studied risk assessment, physical security, emergency management, crisis response, and protection of public…","html":"<p>A Purdue CIT homeland security course where I studied risk assessment, physical security, emergency management, crisis response, and protection of public and private infrastructure.</p>\n<h3>What this was</h3>\n<p>CNIT 51100 explored homeland security from an interdisciplinary perspective, including prevention, mitigation, preparation, response, and recovery. The course connected security planning to real-world infrastructure, emergency management, business continuity, crisis communication, and collaborative response.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Studied how organizations identify assets, evaluate risk, and decide which controls are worth implementing.</li>\n<li>Practiced thinking through physical security from both attacker and defender perspectives.</li>\n<li>Participated in an authorized venue security assessment connected to a Purdue football game environment.</li>\n<li>Connected field observations to emergency management, access control, communication, and business continuity concepts.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course expanded my view of security beyond computers and networks. It showed me how physical access, crowd movement, emergency planning, communication, and risk management all affect the security of real places and critical operations.</p>"}},{"node":{"frontmatter":{"title":"CNIT 47000 Incident Response Management","description":"An incident response course where I am studying IDS concepts, log analysis, network flows, anomaly detection, remediation, and enterprise response planning.","tech":["Incident Response","IDS","Log Analysis","Network Flows"],"github":"","external":"","icon":"Terminal","date":"2026-12-01","order":5,"highlightOrder":5},"excerpt":"A final-semester Purdue CIT incident response course focused on detecting anomalous behavior, analyzing network flows and system logs, and connecting…","html":"<p>A final-semester Purdue CIT incident response course focused on detecting anomalous behavior, analyzing network flows and system logs, and connecting technical response work to business operations.</p>\n<h3>What this is</h3>\n<p>CNIT 47000 connects business operations with the IT and security systems that support day-to-day work. The course focuses on intrusion detection, incident handling, remediation, and the standards and processes behind enterprise-level response plans.</p>\n<h3>What I am focusing on</h3>\n<ul>\n<li>Expanding my hands-on experience with IDS concepts, log analysis, and SIEM-style monitoring workflows.</li>\n<li>Studying how anomalous behavior appears across network flows, system logs, alerts, and reports.</li>\n<li>Connecting technical findings to incident response plans, remediation actions, and business requirements.</li>\n<li>Practicing how causal analysis can support continuous improvement after an incident.</li>\n</ul>\n<h3>Why it matters</h3>\n<p>This course lines up with my blue-team and SIEM interests. It helps connect detection, alert triage, response planning, remediation, and business impact into one practical incident response workflow.</p>"}},{"node":{"frontmatter":{"title":"CNIT 24200 System Administration","description":"A foundational systems administration course where I built hands-on experience with Windows Server, Active Directory, virtualization, backups, storage, and troubleshooting.","tech":["Windows Server","Active Directory","Virtualization","Backup and Storage"],"github":"","external":"","icon":"Server","date":"2024-05-01","order":12,"highlightOrder":10},"excerpt":"A foundational Purdue CIT systems administration course where I built hands-on experience with Windows Server, Active Directory, virtualization, storage…","html":"<p>A foundational Purdue CIT systems administration course where I built hands-on experience with Windows Server, Active Directory, virtualization, storage, backups, and troubleshooting.</p>\n<h3>What this was</h3>\n<p>CNIT 24200 introduced the core systems administration skills behind cybersecurity, networking, IT operations, and infrastructure work. The course focused on managing enterprise-style Windows client and server environments while connecting authentication, authorization, system security, and reliability.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Managed users, groups, organizational units, and group policy concepts in Windows Server environments.</li>\n<li>Practiced system administration tasks across virtualization, SSH access, storage planning, backups, and troubleshooting.</li>\n<li>Studied enterprise infrastructure fundamentals, including directory services, authentication, authorization, and system management.</li>\n<li>Connected server administration decisions to reliability, security, and long-term maintainability.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This class became one of the major starting points for my cybersecurity path and teaching assistant work. It gave me the foundation to understand how real environments are built, managed, secured, backed up, and repaired when something goes wrong.</p>"}},{"node":{"frontmatter":{"title":"CNIT 47100 Vulnerability Analysis and Testing","description":"An authorized security testing course where I practiced vulnerability analysis, controlled exploit testing, endpoint defense awareness, AI security concepts, and responsible documentation.","tech":["Vulnerability Analysis","Penetration Testing","Endpoint Defense","AI Security"],"github":"","external":"","icon":"Bug","date":"2026-05-01","order":4,"highlightOrder":4},"excerpt":"A Purdue CIT security testing course where I practiced authorized vulnerability analysis, controlled exploit testing, endpoint defense awareness, AI…","html":"<p>A Purdue CIT security testing course where I practiced authorized vulnerability analysis, controlled exploit testing, endpoint defense awareness, AI security concepts, and responsible security documentation.</p>\n<h3>What this was</h3>\n<p>CNIT 47100 introduced advanced security testing methods in a controlled lab environment. The course focused on how weaknesses are identified, how defenders evaluate exposure, and how testing can be performed ethically without putting real systems or networks at risk.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Practiced vulnerability analysis and penetration testing workflows in authorized lab scenarios.</li>\n<li>Studied how payload behavior, endpoint protection, and detection gaps can affect Windows environments.</li>\n<li>Explored security weaknesses in emerging AI systems, including model behavior, input handling, and abuse cases.</li>\n<li>Connected offensive testing techniques back to defensive controls, documentation, and corrective action.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course helped me understand penetration testing as more than breaking into systems. The bigger lesson was learning how to test carefully, explain risk clearly, and use offensive security knowledge to improve defensive decision-making.</p>"}},{"node":{"frontmatter":{"title":"CNIT 34220 Network Administration","description":"A network administration course where I configured Unix-based services, firewalls, DNS, mail, web services, proxies, and secure distributed infrastructure.","tech":["Unix Services","DNS and Mail","Firewalls","Proxies"],"github":"","external":"","icon":"Cloud","date":"2026-05-01","order":8,"highlightOrder":8},"excerpt":"A Purdue CIT network administration course where I configured Unix-based network services and practiced securing distributed systems with firewalls…","html":"<p>A Purdue CIT network administration course where I configured Unix-based network services and practiced securing distributed systems with firewalls, service hardening, and secure protocols.</p>\n<h3>What this was</h3>\n<p>CNIT 34220 focused on the installation, administration, and maintenance of distributed computing systems. The course connected network operating systems, interoperability, and service infrastructure through hands-on lab work.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Configured and maintained network services such as DNS, mail, web services, and related server components.</li>\n<li>Studied SNMP, mail protocols, proxies, DMZ service placement, and secure network design.</li>\n<li>Practiced securing servers and services with firewall rules, service hardening, and safer protocol choices.</li>\n<li>Documented lab work and troubleshooting steps for network service implementation.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course helped me understand how network services are built, exposed, monitored, and secured. It connected server administration to the practical security decisions behind websites, mail systems, DMZs, proxies, and distributed infrastructure.</p>"}},{"node":{"frontmatter":{"title":"CNIT 45500 Network Security","description":"A network security course where I am studying VPNs, firewalls, authentication, encryption, wireless security, packet filtering, and secure network architecture.","tech":["VPNs","Firewall Policy","Packet Filtering","Network Security"],"github":"","external":"","icon":"ShieldLock","date":"2026-12-01","order":7,"highlightOrder":7},"excerpt":"A final-semester Purdue CIT network security course focused on VPNs, firewall strategy, authentication, encryption, wireless security, packet filtering…","html":"<p>A final-semester Purdue CIT network security course focused on VPNs, firewall strategy, authentication, encryption, wireless security, packet filtering, and secure network architecture.</p>\n<h3>What this is</h3>\n<p>CNIT 45500 explores the business, conceptual, and technical sides of securing voice and data networks. The course focuses on analyzing weaknesses, designing secure infrastructure, and applying policy-driven network security controls.</p>\n<h3>What I am focusing on</h3>\n<ul>\n<li>Deepening my understanding of VPN design, secure remote access, and firewall rule strategy.</li>\n<li>Studying packet filtering, authentication, encryption, wireless security, and security protocols.</li>\n<li>Connecting network security architecture to business requirements and operational constraints.</li>\n<li>Practicing how to evaluate systems, identify weaknesses, and design more secure infrastructure.</li>\n</ul>\n<h3>Why it matters</h3>\n<p>This course ties directly into the network defense work I want to keep building. It strengthens the connection between routing, segmentation, access control, policy, and real-world security architecture.</p>"}},{"node":{"frontmatter":{"title":"Honeypot and Firewall Homelab","description":"A defensive homelab branch where I test honeypots, firewall rules, VLAN segmentation, VPN access, logging, and directory-aware administration.","tech":["Honeypots","Firewall Rules","VLANs","VPN Access","Active Directory"],"github":"https://github.com/esixtosr/12U-Bare-Metal-Homelab","external":"","icon":"ShieldLock","date":"2026-08-01","order":1,"highlightOrder":1},"excerpt":"A security-focused branch of my homelab where I test honeypots, firewall rules, VLAN segmentation, VPN access, logging, and directory-aware infrastructure…","html":"<p>A security-focused branch of my homelab where I test honeypots, firewall rules, VLAN segmentation, VPN access, logging, and directory-aware infrastructure design.</p>\n<h3>What this was</h3>\n<p>This project extends my larger bare-metal homelab into a controlled defensive security environment. The goal is to understand how exposed services behave, how network controls limit access, and how segmentation can protect infrastructure while still allowing remote access for trusted users.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Tested honeypot concepts to observe suspicious behavior and understand what exposed services can attract.</li>\n<li>Built and adjusted firewall rules to control traffic between lab systems, VLANs, and remote access paths.</li>\n<li>Practiced VLAN segmentation to separate services, users, management access, and testing environments.</li>\n<li>Connected VPN access and directory concepts to role-based access and safer administration.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This lab helped me move from building infrastructure to defending it. It strengthened my understanding of how firewall policy, segmentation, identity, logging, and controlled test systems can work together to support blue-team learning and incident response practice.</p>"}},{"node":{"frontmatter":{"title":"n8n Security Automation Lab","description":"An in-progress automation lab where I use n8n to test email triage, content monitoring, workflow routing, and blue-team response ideas.","tech":["n8n","Workflow Automation","Email Triage","Incident Response"],"github":"","external":"","icon":"Waypoints","date":"2026-12-01","order":17,"highlightOrder":6},"excerpt":"An in-progress automation lab using n8n to experiment with workflow routing, email triage, content monitoring, and blue-team response ideas. What this is…","html":"<p>An in-progress automation lab using n8n to experiment with workflow routing, email triage, content monitoring, and blue-team response ideas.</p>\n<h3>What this is</h3>\n<p>This project explores how automation can support personal productivity and security operations. I am using n8n to test workflow ideas around email checks, profile-related updates, content filtering, alert routing, enrichment, and early-stage incident response triage.</p>\n<h3>What I am working on</h3>\n<ul>\n<li>Building and testing workflow ideas for checking email and filtering relevant messages.</li>\n<li>Exploring how automation can monitor content streams such as comments, feeds, and profile-related activity.</li>\n<li>Experimenting with blue-team triage patterns, including alert routing, enrichment, and response steps.</li>\n<li>Practicing where automation helps and where human review still matters.</li>\n</ul>\n<h3>What I am learning</h3>\n<p>This project is helping me understand automation as a security operations tool. The biggest lesson so far is that useful automation is not just about connecting apps. It requires clear triggers, reliable filtering, useful context, and guardrails so the workflow supports decisions instead of creating noise.</p>"}},{"node":{"frontmatter":{"title":"3D-Printed TrueNAS Homelab","description":"A custom NAS and self-hosting lab built with a 3D-printed enclosure, TrueNAS storage, backups, Jellyfin testing, and Active Directory experimentation.","tech":["TrueNAS","Storage","Active Directory","Self-Hosting"],"github":"https://github.com/esixtosr/3D-Printed-TRUENAS","external":"","icon":"HardDrive","date":"2025-12-01","order":19,"highlightOrder":3},"excerpt":"A custom 3D-printed NAS project built as a personal homelab platform for storage, backups, self-hosted services, and Active Directory experimentation. What…","html":"<p>A custom 3D-printed NAS project built as a personal homelab platform for storage, backups, self-hosted services, and Active Directory experimentation.</p>\n<h3>What this was</h3>\n<p>This project combined hardware, storage planning, and infrastructure services into one small-form-factor NAS build. The goal was to create a practical lab environment for learning how storage, directory services, backups, and self-hosted applications fit into a real network.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Built a custom NAS platform around a 3D-printed enclosure and TrueNAS-based storage.</li>\n<li>Used the system as a foundation for file storage, backups, and self-hosted service experiments.</li>\n<li>Experimented with Jellyfin to test media access, storage behavior, and self-hosted service hosting from the NAS.</li>\n<li>Connected the NAS lab to Windows Server and Active Directory domain controller learning.</li>\n<li>Documented hardware choices, configuration decisions, and infrastructure design in GitHub.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This project helped me connect physical infrastructure with systems administration. It showed how storage, identity, backups, and self-hosted services depend on careful planning, reliable hardware, and clear documentation.</p>"}},{"node":{"frontmatter":{"title":"WiFi Pineapple Mark VII Wireless Security Lab","description":"A controlled wireless security lab where I studied Wi-Fi attack surfaces, rogue access point behavior, client trust, captive portal risks, and defensive awareness.","tech":["Wireless Security","Rogue AP Awareness","Reconnaissance","Captive Portals"],"github":"","external":"","icon":"Router","date":"2025-12-01","order":18,"highlightOrder":2},"excerpt":"A personal wireless security lab using the Hak5 WiFi Pineapple Mark VII to study Wi-Fi attack surfaces, rogue access point behavior, client trust, and…","html":"<p>A personal wireless security lab using the Hak5 WiFi Pineapple Mark VII to study Wi-Fi attack surfaces, rogue access point behavior, client trust, and defensive awareness in controlled environments.</p>\n<h3>What this was</h3>\n<p>This project used the WiFi Pineapple Mark VII as a learning platform for understanding how wireless networks can be audited, monitored, misconfigured, and defended. I focused on how devices discover and trust networks, how access points and clients appear in the wireless environment, and why scope control matters during security testing.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Explored wireless reconnaissance concepts using access point and client visibility.</li>\n<li>Studied rogue access point and captive portal behavior from a defensive awareness perspective.</li>\n<li>Practiced thinking through deauthentication risk, network disruption, and why wireless testing must stay controlled and authorized.</li>\n<li>Reviewed how modular tooling and repeatable workflows can support structured wireless security assessments.</li>\n</ul>\n<h3>What I learned</h3>\n<p>The biggest takeaway was that wireless security is not only about passwords. Client behavior, signal exposure, access point impersonation, network segmentation, monitoring, and user awareness all affect real-world risk. This lab helped me connect wireless attack concepts to safer network design, defensive monitoring, and security awareness training.</p>"}}]}}}