Skip to main content

Overview

The Snow integration enables ThreatAware to collect read-only data from your Snow platform, providing visibility into software assets and helping validate your software asset management controls.
Connection Method: API with Firewall Configuration Setup Time: 20 minutes Access Required: Snow Administrator account

Data collected

The Snow integration provides:
  • Software asset inventory
  • License information
  • Asset usage patterns
  • Compliance tracking data

Use cases

Software Asset Tracking

Monitor software installations and usage across your environment

License Management

Track and validate software licenses to ensure compliance

Asset Inventory

Maintain an accurate inventory of software assets

Compliance Monitoring

Verify software deployment meets organisational standards

Setup instructions

1

Log in to ThreatAware

Access the ThreatAware dashboard and navigate to Settings → Integrations.
2

Locate Snow Integration

Use the search bar to find Snow in the integrations list.
3

Create API User in Snow

Log in to the Snow Management and Configuration Center with an administrator account.
  • Create a new user account
  • Assign the role API Users
  • Document the username and password for later use
4

Configure Firewall Rules

Set up firewall port forwarding to the Snow server:
  • Create a port forward on your firewall to the Snow server
  • Restrict access to ThreatAware’s current allowlist IP addresses, available in-product under Settings → Integrations → AWS Account / IP Whitelist Info
Only allow connections from ThreatAware’s IP addresses. Do not open the port to all traffic.
5

Configure in ThreatAware

Click Connect in the integration setup.
  • Enter the Public IP Address of the Snow server
  • Enter the Forwarded Port configured on your firewall
  • Enter the Username and Password for the Snow API user
  • Click Connect to establish the integration
6

Verify Connection

After connecting, verify the integration status:
  • Check that the Integration Status shows as Active
  • Wait for initial data synchronization (typically 1 hour)
  • Verify data appears in ThreatAware

Required credentials

Field Name: Snow Server Public IP Type: String Description: The publicly accessible IP address of your Snow serverExample: 203.0.113.42
Field Name: Snow Forwarded Port Type: Integer Description: The port number configured on your firewall for the Snow serverExample: 8080 or 443
Field Name: Snow API Username Type: String Description: The username for the Snow API user created with the API Users roleExample: threataware-api or svc_snow
Field Name: Snow API Password Type: Password (encrypted) Description: The password for the Snow API user account
Store this credential securely in your organisation’s password manager.

Verification and testing

After setup, verify the integration is working correctly:
  1. Check Integration Status
    • Navigate to Settings → Integrations in ThreatAware
    • Confirm the Snow integration shows Active status
    • Check the last sync timestamp
  2. Verify Firewall Configuration
    • Ensure the firewall port forward is active
    • Test connectivity from the ThreatAware platform
  3. Verify Data Collection
    • Wait for the initial data sync
    • Search for devices in ThreatAware
    • Verify Snow data appears in device details

Troubleshooting

Symptoms: Integration status shows authentication failureSolutions:
  • Verify the Username and Password are correct
  • Ensure the user account is not locked or expired
  • Confirm the Snow API user has the correct role assigned
  • Check that credentials are entered without extra spaces
Symptoms: Integration fails to connect or times outSolutions:
  • Verify the Public IP Address and Forwarded Port are correct
  • Test the connection from a local machine to ensure the port is accessible
  • Check firewall rules allow connections from ThreatAware’s IP addresses
  • Confirm the Snow server is running and accessible
  • Review network connectivity between ThreatAware and your Snow server
Symptoms: Integration connects initially but drops or fails to syncSolutions:
  • Verify firewall rules restrict access only to ThreatAware’s dedicated IPs
  • Check that the port forward is properly configured
  • Ensure the Snow Management and Configuration Center documentation is followed
  • Contact your network team to verify the port forward is active
Symptoms: Integration shows active but no data appearsSolutions:
  • Wait up to 1 hour for initial data sync
  • Verify there is software asset data in Snow to collect
  • Check the API user has the necessary permissions
  • Review integration logs in ThreatAware (contact support if needed)

Additional resources

Snow Documentation

Official Snow documentation for platform guidance

ThreatAware Support

Contact ThreatAware support for integration assistance

Best practices

Security Considerations
  • Create a dedicated service account for ThreatAware in Snow
  • Document credentials in your organisation’s password manager
  • Restrict firewall access to ThreatAware’s IPs only
  • Monitor integration logs for authentication failures
  • Rotate credentials annually per your security policy
Network Configuration
  • Ensure the firewall port forward is configured before attempting connection
  • Use TLS/SSL encryption for the connection when available
  • Monitor network latency between ThreatAware and Snow server
  • Keep firewall rules updated with any ThreatAware IP changes