Difference between revisions of "OWASP Amass Project"

OWASP Amass Project

In-depth DNS Enumeration and Network Mapping written in Go!

The OWASP Amass project was originally created when the project lead was showing organizations what they look like on the Internet, and he noticed that the tools available were returning incomplete results relative to what could be discovered manually. With the identification of this gap in capabilities for security experts, the Amass project was born.

Description

The OWASP Amass project is focused on DNS enumeration and network infrastructure mapping techniques. These techniques include: obtaining subdomain names by scraping web pages, accessing web APIs, recursive brute forcing, crawling web archives, permuting/altering names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a network map of an organization's presence on the Internet.

Amass reaches out to over 30 passive data sources to learn about the DNS namespace of a target domain. By default, Amass validates all the names by performing DNS queries across a pool of DNS resolvers, which spreads out the activity generated by the enumeration. For all IP addresses collected during this process, Amass queries for associated netblocks and ASNs. As additional data sources become available to provide visibility of the Internet, implementations can quickly be developed within Amass due to the simple interfaces worked into the design.

When the enumeration is complete, an Amass suite tool is capable of converting the results into several different formats accepted by popular network graph visualization engines. This aids analysts and infosec experts attempting to quickly identify network layout and external networks being utilized by the target organization.

If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as Neo4j. Additional handlers can easily be implemented in order to support other databases or even custom solutions.

The project has software deliverables that are implemented in the Go programming language. These deliverables include command-line tools and a Go package that can be imported into other software projects. The software is portable across popular operating systems such as Windows, Linux, MacOS, FreeBSD, etc. The command-line tools can be obtained via several mechanisms described on the installation page, such as through a Go development environment, the release binaries, the Snap package manager for Linux systems, and various package managers maintained by other projects.

Licensing

This program is free software: you can redistribute it and/or modify it under the terms of the Apache 2.0 license. OWASP Amass and any contributions are Copyright © by Jeff Foley 2017.

Project Resources

[Source Code]

[What's New (Revision History)]

[Issue Tracker]

Project Leader

Jeff Foley

Classifications

News and Events

• [1 May 2019] Jeff Foley talked about "Discovering Exposure on the Internet" on the CSIAC Webinar.

• [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.

• [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.

• [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.

• [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.

• [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.

• [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.

• [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.

• [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).

• [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.

• [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.