{"id":205,"date":"2025-10-10T16:26:03","date_gmt":"2025-10-10T16:26:03","guid":{"rendered":"https:\/\/sites.wp.odu.edu\/djohn190\/?page_id=205"},"modified":"2026-05-13T05:32:30","modified_gmt":"2026-05-13T05:32:30","slug":"resume","status":"publish","type":"page","link":"https:\/\/sites.wp.odu.edu\/djohn190\/resume\/","title":{"rendered":"Hands-On Labs"},"content":{"rendered":"<a href=\"https:\/\/sites.wp.odu.edu\/djohn190\/wp-content\/uploads\/sites\/39355\/2026\/05\/CYSE-608-Hands-On-Lab-Report-1.pdf\" class=\"pdfemb-viewer\" style=\"\" data-width=\"max\" data-height=\"max\"  data-toolbar=\"bottom\" data-toolbar-fixed=\"off\">CYSE-608-Hands-On-Lab-Report-1<br\/><\/a>\n<p class=\"wp-block-pdfemb-pdf-embedder-viewer\"><\/p>\n\n\n\n<ul>\n<li><strong>Objective:<\/strong> Access the lab environment and confirm basic navigation and tooling.<\/li>\n\n\n\n<li><strong>What I did:<\/strong> Logged in successfully, explored the platform, opened Server Manager, and launched PowerShell.<\/li>\n\n\n\n<li><strong>Outcome\/Result:<\/strong> Established baseline familiarity with the lab environment and Windows Server administration tools.<\/li>\n\n\n\n<li><strong>Security takeaway:<\/strong> Secure administration starts with controlled access to tools like Server Manager and PowerShell, since they can perform privileged actions.<\/li>\n<\/ul>\n\n\n<a href=\"https:\/\/sites.wp.odu.edu\/djohn190\/wp-content\/uploads\/sites\/39355\/2026\/05\/CYSE-608-Hands-On-Lab-Report-2.pdf\" class=\"pdfemb-viewer\" style=\"\" data-width=\"max\" data-height=\"max\"  data-toolbar=\"bottom\" data-toolbar-fixed=\"off\">CYSE-608-Hands-On-Lab-Report-2<br\/><\/a>\n<p class=\"wp-block-pdfemb-pdf-embedder-viewer\"><\/p>\n\n\n\n<ul>\n<li><strong>Objective:<\/strong> Perform core server configuration tasks and begin centralized management setup.<\/li>\n\n\n\n<li><strong>What I did:<\/strong> Checked for Windows Updates, set the correct time zone, switched to a static IP, enabled Remote Desktop, and began the Windows Admin Center install\/configuration workflow.<\/li>\n\n\n\n<li><strong>Outcome\/Result:<\/strong> Improved server reliability by aligning updates, time accuracy, and stable network addressing; enabled remote administration and began centralized management.<\/li>\n\n\n\n<li><strong>Security takeaway:<\/strong> Remote access (RDP) must be treated as a high-risk service. It should be restricted and monitored, not enabled broadly.<\/li>\n<\/ul>\n\n\n<a href=\"https:\/\/sites.wp.odu.edu\/djohn190\/wp-content\/uploads\/sites\/39355\/2026\/05\/CYSE-608-Hands-On-Lab-Report-3.pdf\" class=\"pdfemb-viewer\" style=\"\" data-width=\"max\" data-height=\"max\"  data-toolbar=\"bottom\" data-toolbar-fixed=\"off\">CYSE-608-Hands-On-Lab-Report-3<br\/><\/a>\n<p class=\"wp-block-pdfemb-pdf-embedder-viewer\"><\/p>\n\n\n\n<ul>\n<li><strong>Objective:<\/strong> Deploy DNS and DHCP to support name resolution and automated IP configuration. <\/li>\n\n\n\n<li><strong>What I did:<\/strong> Set a static IP requirement for DNS, installed DNS, created forward and reverse lookup zones, created host and pointer records, installed DHCP, configured DHCP, created a scope, and activated DHCP. <\/li>\n\n\n\n<li><strong>Outcome\/Result:<\/strong> Built a working foundation for reliable network communication using DNS resolution and DHCP leasing. <\/li>\n\n\n\n<li><strong>Security takeaway:<\/strong> DNS\/DHCP are critical dependencies. Poor control of zones\/scopes can impact the entire environment.<\/li>\n<\/ul>\n\n\n<a href=\"https:\/\/sites.wp.odu.edu\/djohn190\/wp-content\/uploads\/sites\/39355\/2026\/05\/CYSE-608-Hands-On-Lab-Report-4.pdf\" class=\"pdfemb-viewer\" style=\"\" data-width=\"max\" data-height=\"max\"  data-toolbar=\"bottom\" data-toolbar-fixed=\"off\">CYSE-608-Hands-On-Lab-Report-4<br\/><\/a>\n<p class=\"wp-block-pdfemb-pdf-embedder-viewer\"><\/p>\n\n\n\n<ul>\n<li><strong>Objective:<\/strong> Build domain services and integrate servers into the domain environment. <\/li>\n\n\n\n<li><strong>What I did:<\/strong> Installed AD DS, promoted domain services, created a reverse lookup zone, validated server IP information, tested connectivity to the domain controller, and joined a Windows Server to the domain. <\/li>\n\n\n\n<li><strong>Outcome\/Result:<\/strong> Established centralized identity management and domain-based control of Windows resources. <\/li>\n\n\n\n<li><strong>Security takeaway:<\/strong> AD becomes a \u201chigh-value target.\u201d Privileged access and authentication controls must be tightly managed in real enterprise environments.<\/li>\n<\/ul>\n\n\n<a href=\"https:\/\/sites.wp.odu.edu\/djohn190\/wp-content\/uploads\/sites\/39355\/2026\/05\/CYSE-608-Hands-On-Lab-Report-5.pdf\" class=\"pdfemb-viewer\" style=\"\" data-width=\"max\" data-height=\"max\"  data-toolbar=\"bottom\" data-toolbar-fixed=\"off\">CYSE-608-Hands-On-Lab-Report-5<br\/><\/a>\n<p class=\"wp-block-pdfemb-pdf-embedder-viewer\"><\/p>\n\n\n\n<ul>\n<li><strong>Objective:<\/strong> Explore AD site\/subnet design and automate identity tasks using PowerShell. <\/li>\n\n\n\n<li><strong>What I did:<\/strong> Worked through site naming and attempted to add sites\/subnets, documented environment limitations, and performed user creation actions using PowerShell including password assignment steps. <\/li>\n\n\n\n<li><strong>Outcome\/Result:<\/strong> Connected network segmentation concepts (sites\/subnets) to AD design and practiced automation for account management. <\/li>\n\n\n\n<li><strong>Security takeaway:<\/strong> Automation improves consistency, but admin scripting must follow least privilege and change control to prevent accidental misconfigurations.<\/li>\n<\/ul>\n\n\n<a href=\"https:\/\/sites.wp.odu.edu\/djohn190\/wp-content\/uploads\/sites\/39355\/2026\/05\/CYSE-608-Hands-On-Lab-Report-6.pdf\" class=\"pdfemb-viewer\" style=\"\" data-width=\"max\" data-height=\"max\"  data-toolbar=\"bottom\" data-toolbar-fixed=\"off\">CYSE-608-Hands-On-Lab-Report-6<br\/><\/a>\n<p class=\"wp-block-pdfemb-pdf-embedder-viewer\"><\/p>\n\n\n\n<ul>\n<li><strong>Objective:<\/strong> Use Group Policy to deploy software and manage client local groups. <\/li>\n\n\n\n<li><strong>What I did:<\/strong> Created an OU, created and shared a network folder, added a software package in the Group Policy Management Editor, ran gpupdate, created a new GPO, configured group preferences, and added users to the local Administrators role. <\/li>\n\n\n\n<li><strong>Outcome\/Result:<\/strong> Demonstrated how Group Policy enforces consistent configuration and software deployment at scale. <\/li>\n\n\n\n<li><strong>Security takeaway:<\/strong> Local admin rights are a major risk. Group Policy must be used carefully to avoid over-privileging users across endpoints.<\/li>\n<\/ul>\n\n\n<a href=\"https:\/\/sites.wp.odu.edu\/djohn190\/wp-content\/uploads\/sites\/39355\/2026\/05\/CYSE-608-Hands-On-Lab-Report-7.pdf\" class=\"pdfemb-viewer\" style=\"\" data-width=\"max\" data-height=\"max\"  data-toolbar=\"bottom\" data-toolbar-fixed=\"off\">CYSE-608-Hands-On-Lab-Report-7<br\/><\/a>\n<p class=\"wp-block-pdfemb-pdf-embedder-viewer\"><\/p>\n\n\n\n<ul>\n<li><strong>Objective:<\/strong> Use Group Policy to manage Windows Defender Firewall settings and logging. <\/li>\n\n\n\n<li><strong>What I did:<\/strong> Created firewall GPOs, enabled\/disabled firewall settings, linked policies, configured firewall behavior, set logging settings, and customized firewall rules through GPO. <\/li>\n\n\n\n<li><strong>Outcome\/Result:<\/strong> Showed centralized enforcement of firewall posture across domain systems. <\/li>\n\n\n\n<li><strong>Security takeaway:<\/strong> Firewall policy is strongest when it is consistent, logged, and scoped. Logging is critical for troubleshooting and detection.<\/li>\n<\/ul>\n\n\n<a href=\"https:\/\/sites.wp.odu.edu\/djohn190\/wp-content\/uploads\/sites\/39355\/2026\/05\/CYSE-608-Hands-On-Lab-Report-8.pdf\" class=\"pdfemb-viewer\" style=\"\" data-width=\"max\" data-height=\"max\"  data-toolbar=\"bottom\" data-toolbar-fixed=\"off\">CYSE-608-Hands-On-Lab-Report-8<br\/><\/a>\n<p class=\"wp-block-pdfemb-pdf-embedder-viewer\"><\/p>\n\n\n\n<ul>\n<li><strong>Objective:<\/strong> Install and configure RDS roles and review remote app configuration. <\/li>\n\n\n\n<li><strong>What I did:<\/strong> Started RDS installation via Add Roles and Features Wizard, monitored installation progress, reviewed gateway option workflow, and reviewed remote apps in the environment. <\/li>\n\n\n\n<li><strong>Outcome\/Result:<\/strong> Built foundational understanding of RDS deployment flow and the role components involved. <\/li>\n\n\n\n<li><strong>Security takeaway:<\/strong> RDS increases remote access capability, but it also increases exposure. Secure deployment requires controlled access, segmentation, and monitoring.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":31240,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"_links":{"self":[{"href":"https:\/\/sites.wp.odu.edu\/djohn190\/wp-json\/wp\/v2\/pages\/205"}],"collection":[{"href":"https:\/\/sites.wp.odu.edu\/djohn190\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sites.wp.odu.edu\/djohn190\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sites.wp.odu.edu\/djohn190\/wp-json\/wp\/v2\/users\/31240"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.wp.odu.edu\/djohn190\/wp-json\/wp\/v2\/comments?post=205"}],"version-history":[{"count":4,"href":"https:\/\/sites.wp.odu.edu\/djohn190\/wp-json\/wp\/v2\/pages\/205\/revisions"}],"predecessor-version":[{"id":280,"href":"https:\/\/sites.wp.odu.edu\/djohn190\/wp-json\/wp\/v2\/pages\/205\/revisions\/280"}],"wp:attachment":[{"href":"https:\/\/sites.wp.odu.edu\/djohn190\/wp-json\/wp\/v2\/media?parent=205"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}