caffix/amass

OWASP Amass

![OWASP Flagship]([***] ![Follow on ]([] ![Chat on ]([]

!https://github.com/owasp-amass/amass/workflows/tests/badge.svg https://pkg.go.dev/badge/github.com/owasp-amass/amass/v4?utm_source=godoc](https://pkg.go.dev/github.com/owasp-amass/amass/v4)  ![CodeFactor]([] ![Maintainability]([] ![codecov]([]

The OWASP Amass Project performs network mapping of *** surfaces and external asset discovery using open source information gathering and active reconnaissance techniques.

Information Gathering Techniques Used:

---

Installation ![Go Version]([***]

You can find some additional installation variations in the https://github.com/owasp-amass/amass/blob/master/doc/install.md.

Prebuilt Packages

1. Simply unzip the https://github.com/owasp-amass/amass/releases/latest
2. Put the precompiled binary into your path
3. Start using OWASP Amass!

Homebrew

bash
brew tap owasp-amass/amass
brew install amass

Docker Container

1. Install Docker
2. Pull the Docker image by running docker pull caffix/amass
3. Run docker run -v OUTPUT_DIR_PATH:/.config/amass/ caffix/amass enum -d example.com

The volume argument allows the Amass graph database to persist between executions and output files to be accessed on the host system. The first field (left of the colon) of the volume option is the amass output directory that is external to Docker, while the second field is the path, internal to Docker, where amass will write the output files.

From Sources

1. Install Go and setup your Go workspace
2. Download OWASP Amass by running go install -v github.com/owasp-amass/amass/v4/...@master
3. At this point, the binary should be in $GOPATH/bin

Documentation https://pkg.go.dev/badge/github.com/owasp-amass/amass/v4?utm_source=godoc](https://pkg.go.dev/github.com/owasp-amass/amass/v4)

Use the https://github.com/owasp-amass/amass/blob/master/doc/install.md to get started.

Go to the https://github.com/owasp-amass/amass/blob/master/doc/user_guide.md for additional information.

See the https://github.com/owasp-amass/amass/blob/master/doc/tutorial.md for example usage.

See the https://github.com/owasp-amass/amass/blob/master/doc/scripting.md for greater control over your enumeration process.

Troubleshooting ![Chat on ]([]

If you need help with installation and/or usage of the tool, please join our *** server where community members can best help you.

Please avoid opening GitHub issues for support requests or questions!

Contributing ![Chat on ]([]

We are always happy to get new contributors on board! Please check https://github.com/owasp-amass/amass/blob/master/CONTRIBUTING.md to learn how to contribute to our codebase, and join our *** Server to discuss current project goals.

Testimonials

Accenture

"Accenture’s adversary simulation team has used Amass as our primary tool suite on a variety of external enumeration projects and *** surface assessments for clients. It’s been an absolutely invaluable basis for infrastructure enumeration, and we’re really grateful for all the hard work that’s gone into making and maintaining it – it’s made our job much easier!"

- Max Deighton, Accenture Cyber Defense Manager

Visma

"For an internal red team, the organisational structure of Visma puts us against a unique challenge. Having sufficient, continuous visibility over our external *** surface is an integral part of being able to efficiently carry out our task. When dealing with hundreds of companies with different products and supporting infrastructure we need to always be on top of our game.

For years, OWASP Amass has been a staple in the asset reconnaissance field, and keeps proving its worth time after time. The tool keeps constantly evolving and improving to adapt to the new trends in this area."

- Joona Hoikkala (https://github.com/joohoi) & Alexis Fernández (https://github.com/six2dez), Visma Red Team

References ![DEF CON 30 Recon Village]([] ![DEF CON 28 Red Team Village]([] ![DEF CON 27 Demo Labs]([***]

Did you write a blog post, magazine article or do a podcast about OWASP Amass? Or maybe you held or joined a conference talk or meetup session, a hacking workshop or public training where this project was mentioned?

Add it to our ever-growing list of https://github.com/owasp-amass/amass/blob/master/REFERENCES.md by forking and opening a Pull Request!

Top Mentions

• Phillip Wylie | Securing APIs Through External *** Surface Management (EASM)
• Kento Stewart | Mapping Your External Perimeter during an Incident with OWASP Amass
• WhoisXML API | OWASP Amass and WhoisXML API Are Now Integration Partners
• Intigriti | Hacker tools: Amass – Hunting for Subdomains
• Hakluke | Guide to Amass — How to Use Amass More Effectively for Bug Bounties
• SecurityTrails | OWASP Amass: A Solid Information Gathering Tool
• TrustedSec | Upgrade Your Workflow, Part 1: Building OSINT Checklists
• SANS ISC | Offensive Tools Are For Blue Teams Too
• Jason Haddix | LevelUp 0x02 - The Bug Hunters Methodology v3(ish)
• Daniel Miessler | amass — Automated *** Surface Mapping
• Dionach | How to Use OWASP Amass: An Extensive Tutorial
• nynan | How to Actually Use Amass More Effectively — Bug Bounty
• ToolWar | Extreme Subdomain Enumeration/Scanning on Windows : OWASP Amass

Licensing ![License]([***]

This program is free software: you can redistribute it and/or modify it under the terms of the https://github.com/owasp-amass/amass/blob/master/LICENSE. OWASP Amass and any contributions are Copyright © by Jeff Foley 2017-2023. Some subcomponents have separate licenses.