For normal operation, Nodeware requires an outbound HTTPS connection over port 443 to several endpoints, the primary ending in nodeware.zone. Nodeware does not require any inbound ports to be opened at the firewall.
A whitelist entry can be created in a network control device, such as a firewall, using the wildcard:
*.nodeware.zone:443
Additional URLs for Nodeware Agents
There are several endpoints used by Nodeware Agents that are hosted on AWS S3, the URLs and purposes are listed below. These requirements will be deprecated in the future, as they transition to subdomains of the above listed nodeware.zone domain.
Content (scan definition) downloads
nodeware-arsenal.s3.amazonaws.com
Deep scan results return upload
nodeware-results.s3.amazonaws.com
Patch verification and testing downloads
cab-files-patching-and-remediation.s3.amazonaws.com
HTTPS Inspection
Nodeware will not function properly if it detects any tampering of network traffic, including but not limited to HTTPS inspection or the use of SSL certificate rewriting. While we recognize DPI as an important function of network security, we consider the information transmitted by the Nodeware Sensor to be highly confidential and therefore require that it be exempted from such systems.
If you have any questions about network requirements or unusual traffic associated with a Nodeware Sensor, please click Support at the bottom right of this page.
Comments
0 comments
Please sign in to leave a comment.