{
    "componentChunkName": "component---src-pages-archive-js",
    "path": "/archive/",
    "result": {"data":{"allMarkdownRemark":{"edges":[{"node":{"frontmatter":{"date":"2023-12-01","title":"Raspberry Pi Facial Recognition Magic Mirror","tech":["Raspberry Pi","Facial Recognition","Linux","Hardware Prototyping"],"company":"Purdue CIT Coursework","focus":"Embedded Systems Prototype","term":"Project","order":13,"github":"","external":""},"html":"<p>A Raspberry Pi-based smart mirror prototype from CNIT 17600 where I experimented with small-form-factor computing, camera input, Linux setup, and facial recognition.</p>\n<h3>What this was</h3>\n<p>This project came out of CNIT 17600 Information Technology Architectures, an introductory Purdue CIT course that used Raspberry Pi labs to explore operating systems, networked systems, distributed architectures, and how IT components work together.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Set up a Raspberry Pi as the base device for a smart mirror-style prototype.</li>\n<li>Experimented with facial recognition as the main interactive feature.</li>\n<li>Connected hardware setup, operating system configuration, and application behavior into one working project.</li>\n<li>Kept the build afterward as a reminder of my early hands-on work with physical computing.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This was an early technical build, not a major cybersecurity milestone, but it helped me get comfortable with Raspberry Pi hardware, Linux-style setup work, and how software depends on the device, operating system, and architecture underneath it.</p>"}},{"node":{"frontmatter":{"date":"2023-12-01","title":"CNIT 17600 Information Technology Architectures","tech":["Operating Systems","Network Operating Systems","Distributed Systems","IT Architecture"],"company":"Purdue CIT Coursework","focus":"IT Architecture Foundations","term":null,"order":14,"github":"","external":""},"html":"<p>An introductory Purdue CIT course where I started learning how modern IT systems are organized, including operating systems, networked systems, distributed systems, and application architecture.</p>\n<h3>What this was</h3>\n<p>CNIT 17600 introduced the core architecture pieces behind IT environments. The course covered operating systems, network operating systems, distributed systems, distributed applications, and how different technologies work together across an IT stack.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Studied how operating systems, networked systems, and distributed architectures fit together.</li>\n<li>Worked through Raspberry Pi-based labs that connected course concepts to physical hardware.</li>\n<li>Explored how devices, services, and applications interact across an IT environment.</li>\n<li>Built early hands-on confidence before moving deeper into systems, networking, and security coursework.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course gave me an early foundation for thinking about IT systems as connected layers instead of isolated tools. It was not my biggest cybersecurity turning point, but it helped prepare me for later work in system administration, networking, infrastructure, and security.</p>"}},{"node":{"frontmatter":{"date":"2023-12-01","title":"CNIT 18200 System and Organizational Security","tech":["Security Governance","Risk Management","Business Continuity","Incident Management"],"company":"Purdue CIT Coursework","focus":"Organizational Security","term":null,"order":15,"github":"","external":""},"html":"<p>An introductory Purdue CIT security course where I studied how cybersecurity connects to system design, organizational risk, governance, business continuity, and incident planning.</p>\n<h3>What this was</h3>\n<p>CNIT 18200 introduced the organizational side of cybersecurity. The course focused on how security decisions affect systems throughout their life cycle, from planning and design to testing, maintenance, and risk management.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Studied how cybersecurity fits into system design, procurement, testing, and maintenance.</li>\n<li>Explored how governance, compliance, and policy decisions affect organizational security.</li>\n<li>Reviewed business continuity, disaster recovery, and incident management as parts of security planning.</li>\n<li>Practiced thinking through risk models and how analysis supports better security decisions.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course helped me see cybersecurity as more than technical defense. It introduced the governance and risk side of security, including how organizations plan for incidents, support continuity, and make decisions that protect their mission.</p>"}},{"node":{"frontmatter":{"date":"2024-05-01","title":"CNIT 24200 System Administration","tech":["Windows Server","Active Directory","Virtualization","Backup and Storage"],"company":"Purdue CIT Coursework","focus":"Systems Administration","term":null,"order":12,"github":"","external":""},"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":{"date":"2024-05-01","title":"CNIT 15501 Introduction to Software Development Concepts","tech":["Programming Fundamentals","Debugging","Algorithmic Thinking","Software Testing"],"company":"Purdue CIT Coursework","focus":"Software Development Foundations","term":null,"order":13,"github":"","external":""},"html":"<p>An introductory Purdue CIT software development course where I practiced programming fundamentals, debugging, algorithmic thinking, and structured problem solving.</p>\n<h3>What this was</h3>\n<p>CNIT 15501 introduced the core software development concepts that carry across programming languages. The course covered variables, data types, operators, decisions, loops, functions, arrays, basic user interface construction, programming standards, testing, and debugging.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Practiced breaking problems into smaller programming steps.</li>\n<li>Used variables, data types, decisions, loops, functions, and arrays in programming exercises.</li>\n<li>Worked through debugging and error tracing to understand why code failed.</li>\n<li>Applied programming standards and testing habits to small software assignments.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course helped build the programming foundation I later used in security labs, scripting, object-oriented coursework, and small personal tools. It was a baseline class, but it made later technical work easier to approach.</p>"}},{"node":{"frontmatter":{"date":"2024-12-01","title":"CNIT 27000 Cybersecurity Fundamentals I","tech":["Wireshark","John the Ripper","Scripting","Introductory Penetration Testing"],"company":"Purdue CIT Coursework","focus":"Cybersecurity Foundations","term":null,"order":14,"github":"","external":""},"html":"<p>A Purdue CIT cybersecurity foundations course where I started connecting security models, risk, vulnerabilities, technical controls, and incident management to hands-on security tools.</p>\n<h3>What this was</h3>\n<p>CNIT 27000 introduced core cybersecurity concepts, including security models, risk, vulnerabilities, technical controls, policy, and incident management. The course helped build a foundation for later security coursework, lab practice, and defensive thinking.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Practiced reading packet captures and network behavior with Wireshark.</li>\n<li>Learned how password auditing tools such as John the Ripper fit into defensive security awareness.</li>\n<li>Worked with scripting and introductory penetration testing concepts in controlled course environments.</li>\n<li>Studied technical controls such as access management, cryptography, firewalls, and policy-driven security.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This class was one of the first courses where cybersecurity felt more hands-on. It helped me connect security models and policy to actual tools, traffic analysis, password security, and the incident response mindset.</p>"}},{"node":{"frontmatter":{"date":"2024-12-01","title":"CNIT 25501 Object-Oriented Programming Introduction","tech":["Object-Oriented Programming","Collections","Exception Handling","Database Connectivity"],"company":"Purdue CIT Coursework","focus":"Object-Oriented Development","term":null,"order":15,"github":"","external":""},"html":"<p>A Purdue CIT programming course where I moved from basic programming into object-oriented design, collections, exception handling, persistence, and more structured software assignments.</p>\n<h3>What this was</h3>\n<p>CNIT 25501 introduced object-oriented software development concepts used across modern programming languages. The course covered methods, arrays and collections, encapsulation, inheritance, polymorphism, exception handling, data persistence, database connectivity, user interface construction, testing, debugging, and teamwork.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Built programming exercises using object-oriented design concepts.</li>\n<li>Practiced working with methods, arrays, collections, and intermediate control structures.</li>\n<li>Studied encapsulation, inheritance, polymorphism, exception handling, and persistence.</li>\n<li>Worked through larger assignments that required planning, testing, debugging, and cleaner code organization.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course helped me think about software as organized systems instead of isolated scripts. It gave me a stronger base for later security tooling, automation, and projects that needed cleaner structure.</p>"}},{"node":{"frontmatter":{"date":"2024-12-01","title":"Reverse Terminal Lab","tech":["Python","Java","Remote Access Concepts","Defensive Awareness"],"company":"Personal Lab","focus":"Controlled Remote Access Concept","term":null,"order":16,"github":"","external":""},"html":"<p>A small controlled lab where I adapted earlier Java and Python coursework into a file-based remote terminal concept to better understand remote access behavior from a defender’s point of view.</p>\n<h3>What this was</h3>\n<p>This was an experimental personal lab inspired by programming coursework. I used it to study how basic remote terminal behavior can work in a controlled environment and why remote access capabilities need to be handled carefully, ethically, and only on systems I own or have permission to test.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Reused programming concepts from Java and Python assignments in a security-focused lab.</li>\n<li>Explored how command input, output handling, and file-based communication can resemble remote access behavior.</li>\n<li>Practiced thinking about how legitimate remote administration concepts can become risky when misused.</li>\n<li>Treated the project as a private learning artifact rather than a public tool.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This helped me understand the defensive side of remote access: why monitoring, permissions, endpoint controls, and user awareness matter. It also reinforced the importance of keeping security experiments authorized, isolated, and documented responsibly.</p>"}},{"node":{"frontmatter":{"date":"2024-12-01","title":"Flipper Zero Wireless Experimentation","tech":["Flipper Zero","ESP32 WiFi Marauder","HID Security","NFC"],"company":"Personal Lab","focus":"Wireless and HID Security","term":null,"order":17,"github":"","external":""},"html":"<p>A personal hardware security lab where I explored Flipper Zero, ESP32 WiFi Marauder, NFC tagging, Bluetooth behavior, wireless trust assumptions, and BadUSB-style human interface device risks.</p>\n<h3>What this was</h3>\n<p>This was a controlled exploration of portable security hardware and the trust assumptions behind wireless devices, NFC, Bluetooth, captive portals, and USB human interface devices. I used the lab to better understand how everyday devices can introduce security risk when users, endpoints, or organizations trust them too easily.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Experimented with Flipper Zero and ESP32 WiFi Marauder in controlled environments.</li>\n<li>Learned about captive portal concepts, wireless spoofing risks, Bluetooth behavior, encryption awareness, and NFC tagging.</li>\n<li>Studied how BadUSB-style input can affect endpoint trust, user behavior, and device control.</li>\n<li>Connected hardware experimentation back to defensive thinking around policy, awareness, monitoring, and acceptable use.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This lab made security feel more physical. It helped me understand that cybersecurity is not only network traffic and software; it also includes hardware, wireless signals, user trust, endpoint behavior, and the everyday devices people plug in or connect to.</p>"}},{"node":{"frontmatter":{"date":"2024-12-01","title":"Kali VMs and CTF Practice","tech":["Kali Linux","Capture the Flag","Traffic Analysis","Wireshark"],"company":"Personal Lab","focus":"Pentesting Practice","term":null,"order":18,"github":"","external":""},"html":"<p>A personal practice track where I started using Kali virtual machines, capture-the-flag exercises, packet analysis, and introductory penetration testing tools in controlled learning environments.</p>\n<h3>What this was</h3>\n<p>This was an early self-directed security practice environment. I used Kali virtual machines and CTF-style exercises to become more comfortable with security tooling, attacker methodology, traffic inspection, and the importance of testing only inside authorized environments.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Set up Kali virtual machines for security learning and practice.</li>\n<li>Worked through capture-the-flag exercises to build problem-solving habits.</li>\n<li>Practiced traffic inspection and packet analysis with Wireshark.</li>\n<li>Explored tools such as Bettercap conceptually within controlled learning scenarios.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This helped bridge coursework and hands-on security practice. It improved my comfort with Linux-based tooling, lab isolation, network observation, and the mindset needed to investigate systems carefully instead of guessing.</p>"}},{"node":{"frontmatter":{"date":"2024-12-01","title":"Early Active Directory Environment","tech":["Active Directory","Virtual Machines","Domain Controller","User Management"],"company":"Personal Lab","focus":"Windows Domain Foundations","term":null,"order":19,"github":"","external":""},"html":"<p>My first self-directed Active Directory environment, built as a small Windows domain lab to practice domain setup, user management, and enterprise-style administration outside of class.</p>\n<h3>What this was</h3>\n<p>This was an early attempt to recreate system administration concepts on my own. I set up a small Active Directory lab with a domain controller, virtual machines, and test users so I could practice beyond the exact structure of CNIT 242.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Built a small Active Directory environment for personal practice.</li>\n<li>Created a domain, test users, and basic identity management structure.</li>\n<li>Used virtualization to experiment without touching production systems.</li>\n<li>Connected classroom system administration concepts to my own repeatable lab setup.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This was one of my first signs that I wanted to go beyond coursework. It helped me understand directory services, user administration, domain structure, and why identity management matters in enterprise environments.</p>"}},{"node":{"frontmatter":{"date":"2025-05-01","title":"CNIT 34400 Network Engineering Fundamentals","tech":["Routing and Switching","VLANs","ACLs","Subnetting"],"company":"Purdue CIT Coursework","focus":"Network Engineering","term":null,"order":9,"github":"","external":""},"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":{"date":"2025-05-01","title":"CNIT 37100 Cyberlaw and Ethics","tech":["Cyberlaw","Ethics","Privacy","Cyber Policy"],"company":"Purdue CIT Coursework","focus":"Cyber Policy & Ethics","term":null,"order":10,"github":"","external":""},"html":"<p>A Purdue CIT course where I studied the legal, ethical, policy, and governance context behind cybersecurity work and cyber operations.</p>\n<h3>What this was</h3>\n<p>CNIT 37100 focused on cyberlaw as the legal framework around cyber activities and cyber operations. The course covered international, constitutional, U.S. federal, state, and regulatory policy issues that shape how cybersecurity professionals operate.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Studied how cyber policy and law shape professional security work.</li>\n<li>Reviewed legal foundations around privacy, speech, jurisdiction, surveillance, and intellectual property.</li>\n<li>Evaluated how legal and ethical boundaries affect cybersecurity decisions.</li>\n<li>Discussed professional responsibility in security, governance, and cyber operations.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course helped me understand that cybersecurity decisions do not happen in a vacuum. Technical work has legal, ethical, and policy boundaries, and security professionals need to understand those boundaries before acting.</p>"}},{"node":{"frontmatter":{"date":"2025-05-01","title":"CNIT 27100 Cybersecurity Fundamentals II","tech":["System Hardening","Access Control","Wireless Security","Cloud Security"],"company":"Purdue CIT Coursework","focus":"Security Controls","term":null,"order":11,"github":"","external":""},"html":"<p>A Purdue CIT cybersecurity course where I continued building foundational security knowledge around hardening systems, technical controls, wireless security, hardware security, and cloud security.</p>\n<h3>What this was</h3>\n<p>CNIT 27100 extended the cybersecurity foundations from earlier coursework. The course surveyed additional security areas and focused on using tools and controls to secure information systems across modern environments.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Studied mandatory access control and secure provisioning concepts.</li>\n<li>Reviewed technical controls used to mitigate threats and vulnerabilities.</li>\n<li>Explored wireless, hardware, cloud, and system-hardening topics.</li>\n<li>Connected policy and governance decisions to high-risk information systems.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course helped expand my view of cybersecurity beyond single tools. It reinforced that securing systems requires layered controls, risk-aware provisioning, policy decisions, and practical hardening work.</p>"}},{"node":{"frontmatter":{"date":"2025-08-01","title":"CNIT 27200 Database Fundamentals","tech":["SQL","Entity Relationship Diagrams","Data Modeling","Normalization"],"company":"Purdue CIT Coursework","focus":"Database Design","term":null,"order":12,"github":"","external":""},"html":"<p>A Purdue CIT database course where I studied relational database design, data modeling, normalization, SQL, and practical database development.</p>\n<h3>What this was</h3>\n<p>CNIT 27200 introduced the fundamentals of relational database design. The course focused on how data is modeled, organized, normalized, queried, and maintained so applications can store and retrieve information reliably.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Designed entity relationship diagrams for business problem domains.</li>\n<li>Practiced writing SQL queries to define, retrieve, manipulate, and test data.</li>\n<li>Studied normalization and data modeling decisions.</li>\n<li>Applied critical thinking to team-based database design work.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course helped me understand how database structure affects applications, reporting, reliability, and security. It gave me a stronger foundation for thinking about data integrity, query design, and how systems depend on well-organized information.</p>"}},{"node":{"frontmatter":{"date":"2025-12-01","title":"CNIT 32300 Basic Cyberforensics","tech":["Digital Forensics","File Systems","Evidence Analysis","Encryption"],"company":"Purdue CIT Coursework","focus":"Digital Forensics","term":null,"order":10,"github":"","external":""},"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":{"date":"2025-12-01","title":"CNIT 51100 Foundations in Homeland Security Studies","tech":["Risk Assessment","Physical Security","Emergency Management","Crisis Response"],"company":"Purdue CIT Coursework","focus":"Risk & Infrastructure Protection","term":null,"order":11,"github":"","external":""},"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":{"date":"2025-12-01","title":"CNIT 37000 Introduction to Cryptography","tech":["Symmetric Cryptography","Asymmetric Cryptography","Hashing","Key Management"],"company":"Purdue CIT Coursework","focus":"Cryptography","term":null,"order":13,"github":"","external":""},"html":"<p>A Purdue CIT cryptography course where I studied encryption, hashing, trust, key management, and how cryptographic choices protect information in secure systems.</p>\n<h3>What this was</h3>\n<p>CNIT 37000 introduced the inner workings of cryptographic primitives and how to use them correctly. The course covered cryptographic algorithms, protocols, encryption, secure hashing, trust in untrusted environments, key management, and algorithm selection.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Studied symmetric and asymmetric encryption concepts.</li>\n<li>Reviewed integrity protection, hashing, and related security properties.</li>\n<li>Explored how trust can be built between parties that do not already trust each other.</li>\n<li>Applied cryptographic thinking to realistic secure communication problems.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course became directly connected to CryptoChat. It helped me think more carefully about encryption choices, key exchange, trust, and why secure communication requires more than simply hiding message content.</p>"}},{"node":{"frontmatter":{"date":"2025-12-01","title":"CNIT 34000 UNIX Administration","tech":["UNIX","Shell Scripting","User Management","System Hardening"],"company":"Purdue CIT Coursework","focus":"UNIX Administration","term":null,"order":14,"github":"","external":""},"html":"<p>A Purdue CIT systems course where I studied UNIX administration, installation, networking, software management, scripting, user management, and system security.</p>\n<h3>What this was</h3>\n<p>CNIT 34000 focused on the practical work involved in administering UNIX-based systems. The course covered installation, networking, software management, scripting, user management, UNIX services, and integration with Windows environments.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Studied the theory and practice of administering UNIX-based operating systems.</li>\n<li>Practiced installation, maintenance, and basic UNIX service administration.</li>\n<li>Worked with user management, software management, and shell scripting concepts.</li>\n<li>Connected UNIX administration to system hardening and cross-platform infrastructure.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course strengthened the systems side of my security foundation. It helped me become more comfortable with UNIX environments, shell scripting, service administration, and the work behind secure, reliable infrastructure.</p>"}},{"node":{"frontmatter":{"date":"2025-12-01","title":"CryptoChat","tech":["Python","X25519","AES-GCM","Wireshark"],"company":"Personal Lab","focus":"Encrypted Messaging","term":null,"order":17,"github":"https://github.com/esixtosr/CryptoChat","external":""},"html":"<p>An encrypted peer-to-peer messaging project that grew out of my cryptography coursework and helped me connect key exchange, authenticated encryption, trust verification, and packet-level validation.</p>\n<h3>What this was</h3>\n<p>CryptoChat is an educational secure messaging project focused on practical communication security concepts. It explores how two peers can exchange keys, derive encryption material, verify identities, and send encrypted messages over a network connection.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Built a Python-based encrypted chat workflow around peer-to-peer messaging concepts.</li>\n<li>Connected cryptography coursework to practical concepts like key exchange, authenticated encryption, and trust verification.</li>\n<li>Used packet inspection to validate that message contents were not visible in transit.</li>\n<li>Documented the project as a portfolio artifact while keeping the scope educational and controlled.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This project helped make cryptography feel concrete. It showed me that secure communication depends on protocol decisions, identity verification, key handling, replay awareness, validation, and clear documentation — not just choosing an encryption algorithm.</p>"}},{"node":{"frontmatter":{"date":"2025-12-01","title":"WiFi Pineapple Mark VII Wireless Security Lab","tech":["Wireless Security","Rogue AP Awareness","Reconnaissance","Captive Portals"],"company":"Personal Lab","focus":"Wireless Security","term":null,"order":18,"github":"","external":""},"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>"}},{"node":{"frontmatter":{"date":"2025-12-01","title":"3D-Printed TrueNAS Homelab","tech":["TrueNAS","Storage","Active Directory","Self-Hosting"],"company":"Personal Lab","focus":"Storage & Self-Hosting","term":null,"order":19,"github":"https://github.com/esixtosr/3D-Printed-TRUENAS","external":""},"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":{"date":"2026-05-01","title":"CNIT 47100 Vulnerability Analysis and Testing","tech":["Vulnerability Analysis","Penetration Testing","Endpoint Defense","AI Security"],"company":"Purdue CIT Coursework","focus":"Vulnerability Analysis","term":null,"order":4,"github":"","external":""},"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":{"date":"2026-05-01","title":"CNIT 34220 Network Administration","tech":["Unix Services","DNS and Mail","Firewalls","Proxies"],"company":"Purdue CIT Coursework","focus":"Network Services","term":null,"order":8,"github":"","external":""},"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":{"date":"2026-05-01","title":"CNIT 42200 Cyber Criminology","tech":["Cybercrime","Criminology","Behavioral Theory","Research Analysis"],"company":"Purdue CIT Coursework","focus":"Cybercrime Behavior","term":null,"order":9,"github":"","external":""},"html":"<p>A Purdue CIT course where I studied cybercriminal behavior through criminological, psychological, sociological, and research-based perspectives.</p>\n<h3>What this was</h3>\n<p>CNIT 42200 focused on cyber criminology and the study of cybercriminal behavior. The course compared traditional crime with newer forms of cybercrime while connecting theory and research to how cyber offenses develop, spread, and are understood.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Compared traditional criminal behavior with newer forms of cybercriminal activity.</li>\n<li>Applied psychological, sociological, and criminological concepts to cybercrime topics.</li>\n<li>Reviewed research on cybercriminal behavior, theory, and offense patterns.</li>\n<li>Practiced thinking about security problems through human behavior, motivation, and social context.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course helped me see cybersecurity as more than tools and systems. Understanding attacker behavior, motivation, and social patterns adds useful context to technical defense, policy, investigation, incident response, and security awareness.</p>"}},{"node":{"frontmatter":{"date":"2026-05-01","title":"CNIT 51200 Managing Resources and Applications for Homeland Security","tech":["Homeland Security","Business Continuity","Preparedness","Information Security"],"company":"Purdue CIT Coursework","focus":"Homeland Security Resources","term":null,"order":10,"github":"","external":""},"html":"<p>A Purdue CIT homeland security course where I studied how public and private organizations manage resources, technologies, preparedness, continuity, and resilience during emergencies.</p>\n<h3>What this was</h3>\n<p>CNIT 51200 focused on how homeland security programs apply and manage resources across public and private sector environments. The course connected preparedness, continuity, technology, privacy, information security, and organizational resilience to real emergency planning scenarios.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Studied how business continuity and redundancy apply during disasters and emergencies.</li>\n<li>Reviewed homeland security resource planning across public and private sector examples.</li>\n<li>Explored how technologies, people, and procedures support preparedness and response.</li>\n<li>Connected homeland security principles to information security, privacy, and organizational resilience.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course helped me connect cybersecurity to larger preparedness and resilience work. It reinforced that protecting systems also means planning for continuity, coordinating resources, and understanding how technical decisions affect people and organizations during emergencies.</p>"}},{"node":{"frontmatter":{"date":"2026-08-01","title":"Honeypot and Firewall Homelab","tech":["Honeypots","Firewall Rules","VLANs","VPN Access","Active Directory"],"company":"Personal Lab","focus":"Defensive Infrastructure","term":null,"order":1,"github":"https://github.com/esixtosr/12U-Bare-Metal-Homelab","external":""},"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":{"date":"2026-08-01","title":"CNIT 48000 Managing Information Technology Projects","tech":["Project Management","Scope Management","Risk Management","Microsoft Project"],"company":"Purdue CIT Coursework","focus":"IT Project Management","term":null,"order":11,"github":"","external":""},"html":"<p>A Purdue CIT project management course where I studied how IT projects are planned, estimated, staffed, communicated, controlled, and delivered.</p>\n<h3>What this was</h3>\n<p>CNIT 48000 introduced the project management skills used to organize and deliver information technology work. The course focused on scope, risk, budget, time, quality, communication, people, procurement, and externally provided services.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Studied core project management terms, processes, and techniques.</li>\n<li>Practiced thinking through scope, risk, time, budget, and quality tradeoffs.</li>\n<li>Used project management software concepts to plan and manage IT work.</li>\n<li>Applied project management thinking to business and technical problems.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course helped me understand why technical work needs planning, communication, and risk management before implementation begins. It gave me a better vocabulary for organizing projects, explaining tradeoffs, and keeping technical work aligned with real constraints.</p>"}},{"node":{"frontmatter":{"date":"2026-12-01","title":"CNIT 47000 Incident Response Management","tech":["Incident Response","IDS","Log Analysis","Network Flows"],"company":"Purdue CIT Coursework","focus":"Incident Response","term":null,"order":5,"github":"","external":""},"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":{"date":"2026-12-01","title":"CNIT 45500 Network Security","tech":["VPNs","Firewall Policy","Packet Filtering","Network Security"],"company":"Purdue CIT Coursework","focus":"Network Security","term":null,"order":7,"github":"","external":""},"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":{"date":"2026-12-01","title":"CNIT 38101 Enterprise Information Governance","tech":["Information Governance","Policy","Risk","Enterprise Systems"],"company":"Purdue CIT Coursework","focus":"Information Governance","term":null,"order":12,"github":"","external":""},"html":"<p>A Purdue CIT variable-title course where I studied enterprise information governance, policy, risk, and the organizational context around information systems.</p>\n<h3>What this was</h3>\n<p>CNIT 38101 was a variable-title Purdue CIT course focused on enterprise information governance. I am keeping this archive entry focused on governance, policy, risk, accountability, and how organizations manage information systems responsibly.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Studied enterprise information governance as a bridge between technical systems and organizational policy.</li>\n<li>Reviewed how cybersecurity and systems coursework connect to governance topics.</li>\n<li>Considered how information handling, risk, and accountability affect enterprise environments.</li>\n<li>Built context for later work involving security policy, compliance, and organizational decision-making.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This course fit into the governance side of my cybersecurity path. It helped me understand security and information management as enterprise responsibilities, not only technical tasks handled after systems are already built.</p>"}},{"node":{"frontmatter":{"date":"2026-12-01","title":"12U Bare-Metal Homelab","tech":["UniFi","Proxmox","VLANs","Bare Metal"],"company":"Personal Lab","focus":"Infrastructure Homelab","term":null,"order":13,"github":"https://github.com/esixtosr/12U-Bare-Metal-Homelab","external":""},"html":"<p>A compact 12U bare-metal homelab built to support network segmentation, infrastructure services, virtualization, and hands-on systems administration.</p>\n<h3>What this was</h3>\n<p>This build combines physical server hardware, UniFi networking, managed switching, VLAN planning, and documentation-focused topology work into one reusable lab environment. It supports cybersecurity, networking, systems administration, and self-hosted service practice.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Built a compact rack environment around physical infrastructure and managed networking.</li>\n<li>Used UniFi networking and VLAN planning to segment lab services and traffic.</li>\n<li>Practiced virtualization and infrastructure service design with Proxmox and bare-metal systems.</li>\n<li>Documented topology, port connections, and network architecture decisions.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This homelab became a foundation for many later security and infrastructure experiments. It helped me connect networking, hardware, virtualization, segmentation, and documentation into one repeatable environment.</p>"}},{"node":{"frontmatter":{"date":"2026-12-01","title":"NetFlow","tech":["React","JavaScript","Network Engineering","GitHub Pages"],"company":"Personal Lab","focus":"Network Visualization","term":null,"order":14,"github":"https://github.com/esixtosr/NetFlow","external":"https://esixtosr.github.io/NetFlow/network/home-lab/"},"html":"<p>An interactive network topology visualization tool inspired by Cisco Packet Tracer, built to map infrastructure layouts, visualize VLAN segmentation, and document network architectures.</p>\n<h3>What this was</h3>\n<p>NetFlow is a web-based tool for creating devices, defining connections, organizing VLAN environments, and exporting network diagrams for documentation and analysis. It grew out of the need to represent real homelab infrastructure more clearly.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Built an interactive topology interface using React and JavaScript.</li>\n<li>Modeled network devices, connections, VLAN environments, and lab infrastructure layouts.</li>\n<li>Published the tool with GitHub Pages for easier viewing and sharing.</li>\n<li>Connected network engineering practice to clearer documentation and visual communication.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This project helped me turn network design into something more understandable and inspectable. It strengthened both my frontend skills and my ability to document technical infrastructure in a way that supports troubleshooting and explanation.</p>"}},{"node":{"frontmatter":{"date":"2026-12-01","title":"Wazuh Enterprise SIEM Lab","tech":["Wazuh","Active Directory","MITRE ATT&CK","Windows Server"],"company":"Personal Lab","focus":"SIEM Monitoring","term":null,"order":15,"github":"","external":""},"html":"<p>An enterprise-style SIEM lab built to monitor role-based VPN access, Active Directory groups, Windows endpoints, and security telemetry through Wazuh.</p>\n<h3>What this was</h3>\n<p>This lab maps user roles to access paths, collects endpoint agent data, and validates detections such as failed logons and endpoint posture from a centralized dashboard aligned with MITRE ATT&#x26;CK-style analysis.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Set up Wazuh monitoring around Windows endpoints and Active Directory context.</li>\n<li>Connected role-based access concepts to VPN paths and user groups.</li>\n<li>Reviewed failed logon detections and endpoint posture from a centralized dashboard.</li>\n<li>Practiced thinking through how telemetry supports blue-team investigation and response.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This lab helped connect infrastructure administration to detection engineering. It showed how identity, endpoint agents, logs, dashboards, and security frameworks can work together to make activity visible and actionable.</p>"}},{"node":{"frontmatter":{"date":"2026-12-01","title":"Expanded Active Directory and Wazuh Environment","tech":["Active Directory","Wazuh","Windows Server","Endpoint Monitoring"],"company":"Personal Lab","focus":"Identity & SIEM Monitoring","term":null,"order":16,"github":"","external":""},"html":"<p>A more capable Active Directory lab that expanded my earlier domain environment with stronger hardware, additional virtual machines, and Wazuh-based monitoring.</p>\n<h3>What this was</h3>\n<p>This build grew out of my first self-directed Active Directory environment. The earlier version helped me understand domains and users at a small scale; this version pushed the idea further by adding more compute, more endpoints, and a stronger connection to SIEM visibility.</p>\n<h3>What I worked on</h3>\n<ul>\n<li>Expanded the original Active Directory concept into a larger Windows domain environment.</li>\n<li>Added virtual machines and lab resources to support more realistic administration and monitoring activity.</li>\n<li>Connected identity and endpoint activity into Wazuh for centralized visibility.</li>\n<li>Practiced thinking about how domain structure, users, endpoints, and logs fit together in a security lab.</li>\n</ul>\n<h3>What I learned</h3>\n<p>This project showed the progression from basic administration practice to monitored enterprise-style infrastructure. It helped connect Active Directory design with detection, logging, endpoint visibility, and the operational side of defending Windows environments.</p>"}},{"node":{"frontmatter":{"date":"2026-12-01","title":"n8n Security Automation Lab","tech":["n8n","Workflow Automation","Email Triage","Incident Response"],"company":"Personal Lab","focus":"Security Automation","term":null,"order":17,"github":"","external":""},"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>"}}]}},"pageContext":{}},
    "staticQueryHashes": ["1327081361","1833805599","1994492073","2792866897","506348124"]}