firewall - How to evaluate whether a port should be closed or open? -
so meet pci compliance, need have justification every port that's open on windows server 2012 r2. looked @ firewall, , there's ton of rules. started going through each rule , deciding if should closed or not, i'm looking more efficient process.
my goals close ports without disrupting live site in way, , ones can't close, have clear reasoning behind why i've left open.
my first thought check ports being listened using: netstat -aon
but i'm not positive comprehensive @ ports being used - example, there processes use ports sometime , aren't listening on ports other times? ports used scheduled activities, listed here?
the way see it, need figure out firewall rules below not being used server, , able track down service using each rule i've left in rules.
here current active rules. recommendations on process doing correctly?
- nsclient++ monitoring agent
- prtg_network_monitor_admin_tool
- prtg_network_monitor_probe
- prtg_network_monitor_server
- prtg_network_monitor_server
- visual studio 2013 remote debugger discovery (devenv.exe)
- core networking - destination unreachable (icmpv6-in)
- core networking - destination unreachable fragmentation needed (icmpv4-in)
- core networking - dynamic host configuration protocol (dhcp-in)
- core networking - dynamic host configuration protocol ipv6(dhcpv6-in)
- core networking - internet group management protocol (igmp-in)
- core networking - iphttps (tcp-in)
- core networking - ipv6 (ipv6-in)
- core networking - multicast listener done (icmpv6-in)
- core networking - multicast listener query (icmpv6-in)
- core networking - multicast listener report (icmpv6-in)
- core networking - multicast listener report v2 (icmpv6-in)
- core networking - neighbor discovery advertisement (icmpv6-in)
- core networking - neighbor discovery solicitation (icmpv6-in)
- core networking - packet big (icmpv6-in)
- core networking - parameter problem (icmpv6-in)
- core networking - router advertisement (icmpv6-in)
- core networking - router solicitation (icmpv6-in)
- core networking - teredo (icmpv6-in)
- core networking - teredo (udp-in)
- core networking - time exceeded (icmpv6-in)
- file , printer sharing (echo request - icmpv4-in)
- file , printer sharing (echo request - icmpv6-in)
- file , printer sharing (llmnr-udp-in)
- file , printer sharing (nb-datagram-in)
- file , printer sharing (nb-name-in)
- file , printer sharing (nb-session-in)
- file , printer sharing (smb-in)
- file , printer sharing (spooler service - rpc)
- file , printer sharing (spooler service - rpc-epmap)
- file server remote management (dcom-in)
- file server remote management (smb-in)
- file server remote management (wmi-in)
- google chrome (mdns-in)
- remote desktop - shadow (tcp-in)
- remote desktop - user mode (tcp-in)
- remote desktop - user mode (udp-in)
- world wide web services (https traffic-in)
- windows communication foundation net.tcp listener adapter (tcp-in)
- windows remote management (http-in)
- world wide web services (http traffic-in)
Comments
Post a Comment