Separate your outbound NAT to prevent issues with guest wireless traffic

If your organization provides guest wireless network service, issues related to guest traffic may appear on your Scorecard, even though you have no control over guest devices. You can keep those issues off your Scorecard by separating out your outbound network address translation (NAT) IP address.

Deploy a separate guest NAT IP address

A wireless network NAT IP address that is separate and unique from the NAT IP address on your office network routes guest traffic directly out to the internet with a unique digital footprint. Guest traffic never flows on your internal office wireless network, so any potential risk introduced by those unknown devices is neutralized, even if they contain vulnerabilities or have been compromised.

Tell SecurityScorecard about the discrete NAT address

After you deploy a separate NAT IP address for your guest wireless network, tell SecurityScorecard about it and provide the unique IP address:

• Either submit a Support request to request the tagging of the guest NAT address providing:
  +. The scorecard
  +. The IP address
  +. A description of the usage of the IP and any evidence of such.
• Or use the Digital Footprint following this article.

Upon verification and approval, SecurityScorecard will tag the IP so that findings of the Issue types under the Endpoint Security factor will not be raised.