Asset Monitoring

Find the vulnerabilities in your attack surface before remote attackers do!

Keep track of what you’re exposing to the Internet

Exposed subdomains, private git repositories, and open ports that should actually be closed - these are just a few assets which attackers can exploit to gain access to company sensitive information. Asset Monitoring mimics the reconnaissance methods attackers use to map out a target’s attack surface and its potential weaknesses. This powerful web vulnerability scanner automates security modules at scale to cover a wide attack surface, and checks for entry point vulnerabilities that could be chained for more critical vulnerabilities.

Web vulnerability testing executed by Detectify Asset Monitoring:

  • Sensitive file exposure
  • Secrets exposed in page responses including API keys & passwords
  • Single request/response tests for XSS, SSRF, and RCE vulnerabilities
  • Path traversal
  • Exposure of data through internal software (e.g. monitoring)
A computer scanning for domains
Detectify logo

Additional features in Asset Monitoring

But wait, there’s more! Asset Monitoring helps you track technologies and potential subdomain takeovers:

1 list bullet

Fingerprinting technologies - Asset Monitoring will report on the software it discovers to help you stay on top of any changes in your tech stack including rogue installations.

2 list bullet

Monitor subdomain for takeovers - Subdomains pointing to third party services no longer being used make it possible for malicious hackers to register the subdomain on that third party and (effectively) hijack the subdomain.

How does the subdomain monitoring service work?

There are two scenarios in which subdomains are added to Detectify

Scenario 1

You provide us with subdomains

Subdomains from a DNS master file

The customer needs to provide us with the master file for their DNS. This file contains the subdomains they want us to monitor. Initially they need to send us this file via email.

There are some requirements on the file:

It should be formatted as a standard DNS master file (RFC 1034-1035) & it needs to either contain an "$ORIGIN" row or we need to know the root origin for the master file (this is most likely the domain they want to monitor, so example.com if they want to look for subdomain takeover under that)

Get subdomains from a DNS zone transfer (AXFR)

The customer needs to whitelist our external IPs in their DNS for zone transfers. Doing this is dependent on what DNS they are running but this should be among the DNS settings.

The second step is an address or IP for the name server we should use and the zone that we should transfer (most likely the domain they want to monitor, so example.com if they want to look for subdomain takeover under that).

Provide a list of subdomains

The customer needs to provide us with a list of subdomains. We will perform a DNS lookup on each subdomain and they will be populated into our scanners in Asset Monitoring and Deep Scan.

Scenario 2

Detectify finds the subdomains

In this scenario the customer doesn’t have to provide us with any additional information. We will try and use a combination of non-malicious techniques to try to enumerate the subdomains.

Yep. That’s it.

A toolbox full of tools

GO HACK YOURSELF!

We’ll help you prioritize security for thousands of web assets.

Get ethical hacker-powered insight on which company assets are discoverable on the Internet now. Request a live demo of Asset Monitoring and speak with a Detectify online security expert to get started!

Request a demo