Skip to main content

ThreatNG

Discover and monitor your external attack surface with ThreatNG. This integration ingests exposure scores, subdomains, DNS permutations, cloud assets, SaaS vendor identification, code secrets, and TLS/SSL certificate findings to provide visibility into your organization's digital risk posture.

Installation

info

You will need a ThreatNG API key to configure this integration. API keys are provisioned by ThreatNG for your organization. Contact your ThreatNG account representative or reach out to info@threatngsecurity.com to request API access.

To install the ThreatNG integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select ThreatNG. Click New Instance to begin configuring your integration.

Creating an instance requires the following:

  • API Key - Your ThreatNG API key used to authenticate requests. This key is sent via the ApiKey header to the ThreatNG Public API.

  • Domain - The domain you want to monitor (e.g., example.com). ThreatNG scans this domain for external attack surface findings including subdomains, cloud assets, DNS permutations, code secrets, SaaS identification, and TLS/SSL certificates.

  • Polling Interval - Select a frequency that meets your monitoring needs. You may leave this as DISABLED and manually execute the integration.

Click Create once all values are provided to finalize the integration.

What data is ingested?

DataDescription
Exposure ScoreOverall ThreatNG exposure grade and per-category scores (Cyber Risk, BEC & Phishing Susceptibility, Brand Damage, etc.)
SubdomainsDiscovered subdomains for the monitored domain
DNS PermutationsTyposquatting and look-alike domains that are registered (taken), with or without MX records
Code SecretsExposed secrets and credentials found in public code repositories
Cloud DiscoveryCloud assets discovered across AWS, GCP, and other providers, including S3 buckets and storage containers
SaaS IdentificationThird-party SaaS vendors identified as being used by the organization
TLS/SSL CertificatesSummary of TLS/SSL certificate status (total, valid, invalid)

Next steps

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.