{"id":375,"date":"2026-10-14T13:58:57","date_gmt":"2026-10-14T13:58:57","guid":{"rendered":"https:\/\/sites.wp.odu.edu\/cyse200tethan\/?page_id=375"},"modified":"2026-10-16T20:22:34","modified_gmt":"2026-10-16T20:22:34","slug":"windows-firewall-and-group-policy","status":"publish","type":"page","link":"https:\/\/sites.wp.odu.edu\/cyse200tethan\/windows-firewall-and-group-policy\/","title":{"rendered":"Windows Firewall and Group Policy"},"content":{"rendered":"\n

Windows Firewall<\/strong><\/p>\n\n\n\n

The firewall paper mainly covered about how Windows controls network connections. Inbound rules apply to traffic that is coming into the computer. While outbound rules are applying to traffic leaving it.<\/p>\n\n\n\n

I wrote about how allow and block rules work together. An allow rule can make an exception to the default inbound block setting that is there. However, a conflicting block rule will take its priority over that allow rule. So adding an allow rule does not always mean the connection will work.<\/p>\n\n\n\n

This paper also covered the Domain, Private and Public profiles in Windows settings. A rule can apply to one profile or several and this matters because a connection needed on a private network might not be something I want to allow over on a public network.<\/p>\n\n\n\n

TCP\/IP Security Lab<\/strong><\/p>\n\n\n\n

In this lab, I used ipconfig \/all to check the computer\u2019s network settings. I also worked with netstat -ano to look at connections and listening ports. The output included process IDs that could be checked with tasklist.<\/p>\n\n\n\n

The firewall part of the lab used PowerShell. I reviewed the firewall profiles and worked with a temporary inbound block rule for TCP port 5555. The tasks included checking the rule and removing it after testing.<\/p>\n\n\n\n

This lab took place while I was preparing for Security+. It gave me a chance to work with some of the networking and firewall topics I had been studying.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Windows Firewall and Group Policy Lab<\/strong><\/p>\n\n\n\n

I opened Windows Defender Firewall with Advanced Security and checked its three profiles. My report recorded the Domain, Private, and Public profiles as on. I then reviewed existing inbound and outbound rules.<\/p>\n\n\n\n

I created an inbound rule allowing TCP traffic on local port 8080. I disabled the rule and enabled it again to see how its status changed. I also created an outbound rule blocking TCP traffic that used local port 8080.<\/p>\n\n\n\n

For the Group Policy section, I created a rule allowing inbound TCP traffic on port 9090. This rule applied only to the Private profile. I ran gpupdate \/force and used PowerShell to review the profiles and lab rules.<\/p>\n\n\n\n

The lab also had me temporarily disable the Private firewall profile inside the VM. I turned it back on afterward immediately because the risk concern is high if it is disabled. The final task covered removing the temporary rules used during testing.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

What I Learned<\/strong><\/p>\n\n\n\n

Disabling one rule is different from disabling a firewall profile. When I disabled the rule, that rule stopped applying. Turning off the profile removed firewall protection for connections using that profile.<\/p>\n\n\n\n

I had trouble finding the Group Policy settings at first. The instructions included a Policies folder that was not shown in Local Group Policy Editor. Once I found the correct path, I could continue with the rule.<\/p>\n\n\n\n

The port settings also needed careful attention to my knowledge. My outbound rule used local port 8080. That is different from blocking connections to port 8080 on another computer.<\/p>\n\n\n\n

What I Took Away<\/strong><\/p>\n\n\n\n

These labs gave me practice with checking rules instead of only reading about them and not doing anything. I could look at a rule in the console and then find it through PowerShell.<\/p>\n\n\n\n

If a connection is blocked I would check the active profile and the rules that are applied to it. I would not turn off the whole firewall just to get the connection working. I would look for the setting causing the problem first.<\/p>\n\n\n\n

Research Paper and Lab Reports<\/strong><\/p>\n\n\n\n

Windows Firewall Research Assignment<\/p>\n\n\n\n

Windows TCP\/IP Security – Lab 2<\/p>\n\n\n\n

Windows Firewall and Group Policy – Lab Report<\/p>\n","protected":false},"excerpt":{"rendered":"

Windows Firewall The firewall paper mainly covered about how Windows controls network connections. Inbound rules apply to traffic that is coming into the computer. While outbound rules are applying to traffic leaving it. I wrote about how allow and block rules work together. An allow rule can make an exception to the default inbound block… <\/p>\n

Read More<\/a><\/div>\n","protected":false},"author":29393,"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\/cyse200tethan\/wp-json\/wp\/v2\/pages\/375"}],"collection":[{"href":"https:\/\/sites.wp.odu.edu\/cyse200tethan\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sites.wp.odu.edu\/cyse200tethan\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sites.wp.odu.edu\/cyse200tethan\/wp-json\/wp\/v2\/users\/29393"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.wp.odu.edu\/cyse200tethan\/wp-json\/wp\/v2\/comments?post=375"}],"version-history":[{"count":5,"href":"https:\/\/sites.wp.odu.edu\/cyse200tethan\/wp-json\/wp\/v2\/pages\/375\/revisions"}],"predecessor-version":[{"id":410,"href":"https:\/\/sites.wp.odu.edu\/cyse200tethan\/wp-json\/wp\/v2\/pages\/375\/revisions\/410"}],"wp:attachment":[{"href":"https:\/\/sites.wp.odu.edu\/cyse200tethan\/wp-json\/wp\/v2\/media?parent=375"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}