<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Caffix</id>
		<title>OWASP - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Caffix"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php/Special:Contributions/Caffix"/>
		<updated>2026-05-06T10:06:33Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.27.2</generator>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=253524</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=253524"/>
				<updated>2019-08-05T01:42:51Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* OWASP Amass Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration, Attack Surface Mapping and External Asset Discovery!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass Project has developed a tool to help information security professionals perform network mapping of attack surfaces and perform external asset discovery using open source information gathering and active reconnaissance techniques.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Midlevel_projects.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Lab_Projects|Lab Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [31 Jul 2019] OWASP Amass Project shows up in DarkReading &amp;quot;8 Free Tools to Be Showcased at Black Hat and DEF CON&amp;quot; article.&lt;br /&gt;
&lt;br /&gt;
* [1 Jun 2019] Anthony Rhodes and Jeff Foley talked about advanced features and configuration options of Amass at the Bugcrowd LevelUp 0x04 virtual conference.&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Leader:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Miessler'''&lt;br /&gt;
&lt;br /&gt;
* '''Kian Jamali'''&lt;br /&gt;
&lt;br /&gt;
* '''Nikos Gkogkos'''&lt;br /&gt;
&lt;br /&gt;
* '''Jason Haddix'''&lt;br /&gt;
&lt;br /&gt;
* '''Julio Hawthorne'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=253523</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=253523"/>
				<updated>2019-08-04T22:40:25Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Classifications */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass Project has developed a tool to help information security professionals perform network mapping of attack surfaces and perform external asset discovery using open source information gathering and active reconnaissance techniques.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Midlevel_projects.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Lab_Projects|Lab Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [31 Jul 2019] OWASP Amass Project shows up in DarkReading &amp;quot;8 Free Tools to Be Showcased at Black Hat and DEF CON&amp;quot; article.&lt;br /&gt;
&lt;br /&gt;
* [1 Jun 2019] Anthony Rhodes and Jeff Foley talked about advanced features and configuration options of Amass at the Bugcrowd LevelUp 0x04 virtual conference.&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Leader:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Miessler'''&lt;br /&gt;
&lt;br /&gt;
* '''Kian Jamali'''&lt;br /&gt;
&lt;br /&gt;
* '''Nikos Gkogkos'''&lt;br /&gt;
&lt;br /&gt;
* '''Jason Haddix'''&lt;br /&gt;
&lt;br /&gt;
* '''Julio Hawthorne'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=253522</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=253522"/>
				<updated>2019-08-04T22:39:00Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Classifications */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass Project has developed a tool to help information security professionals perform network mapping of attack surfaces and perform external asset discovery using open source information gathering and active reconnaissance techniques.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-lab-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Lab_Projects|Lab Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [31 Jul 2019] OWASP Amass Project shows up in DarkReading &amp;quot;8 Free Tools to Be Showcased at Black Hat and DEF CON&amp;quot; article.&lt;br /&gt;
&lt;br /&gt;
* [1 Jun 2019] Anthony Rhodes and Jeff Foley talked about advanced features and configuration options of Amass at the Bugcrowd LevelUp 0x04 virtual conference.&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Leader:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Miessler'''&lt;br /&gt;
&lt;br /&gt;
* '''Kian Jamali'''&lt;br /&gt;
&lt;br /&gt;
* '''Nikos Gkogkos'''&lt;br /&gt;
&lt;br /&gt;
* '''Jason Haddix'''&lt;br /&gt;
&lt;br /&gt;
* '''Julio Hawthorne'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=253473</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=253473"/>
				<updated>2019-08-01T12:41:32Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* News and Events */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass Project has developed a tool to help information security professionals perform network mapping of attack surfaces and perform external asset discovery using open source information gathering and active reconnaissance techniques.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [31 Jul 2019] OWASP Amass Project shows up in DarkReading &amp;quot;8 Free Tools to Be Showcased at Black Hat and DEF CON&amp;quot; article.&lt;br /&gt;
&lt;br /&gt;
* [1 Jun 2019] Anthony Rhodes and Jeff Foley talked about advanced features and configuration options of Amass at the Bugcrowd LevelUp 0x04 virtual conference.&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Leader:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Miessler'''&lt;br /&gt;
&lt;br /&gt;
* '''Kian Jamali'''&lt;br /&gt;
&lt;br /&gt;
* '''Nikos Gkogkos'''&lt;br /&gt;
&lt;br /&gt;
* '''Jason Haddix'''&lt;br /&gt;
&lt;br /&gt;
* '''Julio Hawthorne'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=253472</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=253472"/>
				<updated>2019-08-01T12:36:29Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass Project has developed a tool to help information security professionals perform network mapping of attack surfaces and perform external asset discovery using open source information gathering and active reconnaissance techniques.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [1 Jun 2019] Anthony Rhodes and Jeff Foley talked about advanced features and configuration options of Amass at the Bugcrowd LevelUp 0x04 virtual conference.&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Leader:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Miessler'''&lt;br /&gt;
&lt;br /&gt;
* '''Kian Jamali'''&lt;br /&gt;
&lt;br /&gt;
* '''Nikos Gkogkos'''&lt;br /&gt;
&lt;br /&gt;
* '''Jason Haddix'''&lt;br /&gt;
&lt;br /&gt;
* '''Julio Hawthorne'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252916</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252916"/>
				<updated>2019-07-09T15:56:55Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass Project has developed a tool to help information security professionals perform network mapping of attack surfaces and perform external asset discovery using open source information gathering and active reconnaissance techniques.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [1 Jun 2019] Anthony Rhodes and Jeff Foley talked about advanced features and configuration options of Amass at the Bugcrowd LevelUp 0x04 virtual conference.&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Leader:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Miessler'''&lt;br /&gt;
&lt;br /&gt;
* '''Kian Jamali'''&lt;br /&gt;
&lt;br /&gt;
* '''Nikos Gkogkos'''&lt;br /&gt;
&lt;br /&gt;
* '''Jason Haddix'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252837</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252837"/>
				<updated>2019-07-05T15:55:07Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass Project has developed a tool to help information security professionals perform network mapping of attack surfaces and perform external asset discovery using open source information gathering and active reconnaissance techniques.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [1 Jun 2019] Anthony Rhodes and Jeff Foley talked about advanced features and configuration options of Amass at the Bugcrowd LevelUp 0x04 virtual conference.&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Leader:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Miessler'''&lt;br /&gt;
&lt;br /&gt;
* '''Kian Jamali'''&lt;br /&gt;
&lt;br /&gt;
* '''Nikos Gkogkos'''&lt;br /&gt;
&lt;br /&gt;
* '''Jason Haddix'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252818</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252818"/>
				<updated>2019-07-04T17:45:43Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass Project has developed a tool to help information security professionals perform network mapping of attack surfaces and perform external asset discovery using open source information gathering and active reconnaissance techniques.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [1 Jun 2019] Anthony Rhodes and Jeff Foley talked about advanced features and configuration options of Amass at the Bugcrowd LevelUp 0x04 virtual conference.&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Leader:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Miessler'''&lt;br /&gt;
&lt;br /&gt;
* '''Kian Jamali'''&lt;br /&gt;
&lt;br /&gt;
* '''Jason Haddix'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252664</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252664"/>
				<updated>2019-06-28T17:17:27Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* OWASP Amass Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass Project has developed a tool to help information security professionals perform network mapping of attack surfaces and perform external asset discovery using open source information gathering and active reconnaissance techniques.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [1 Jun 2019] Anthony Rhodes and Jeff Foley talked about advanced features and configuration options of Amass at the Bugcrowd LevelUp 0x04 virtual conference.&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Leader:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Miessler'''&lt;br /&gt;
&lt;br /&gt;
* '''Kian Jamali'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252663</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252663"/>
				<updated>2019-06-28T17:15:59Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass project was originally created when the project leader 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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [1 Jun 2019] Anthony Rhodes and Jeff Foley talked about advanced features and configuration options of Amass at the Bugcrowd LevelUp 0x04 virtual conference.&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Leader:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Miessler'''&lt;br /&gt;
&lt;br /&gt;
* '''Kian Jamali'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252428</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252428"/>
				<updated>2019-06-17T18:03:35Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* News and Events */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass project was originally created when the project leader 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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [1 Jun 2019] Anthony Rhodes and Jeff Foley talked about advanced features and configuration options of Amass at the Bugcrowd LevelUp 0x04 virtual conference.&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Leader:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252427</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252427"/>
				<updated>2019-06-17T18:02:50Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* News and Events */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass project was originally created when the project leader 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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [1 Jun 2019] Jeff Foley and Anthony Rhodes talked about advanced features and configuration options of Amass at the Bugcrowd LevelUp 0x04 virtual conference.&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Leader:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252426</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=252426"/>
				<updated>2019-06-17T17:59:21Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass project was originally created when the project leader 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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Leader:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=252106</id>
		<title>User:Caffix</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=252106"/>
				<updated>2019-06-04T23:10:48Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.linkedin.com/in/caffix https://www.owasp.org/images/7/7f/Linkedin-button.png]&lt;br /&gt;
[[File:Caffix_BSidesROC.jpeg|left|thumb]]&lt;br /&gt;
&lt;br /&gt;
Jeff Foley is an innovative, results-driven technical leader known for delivering game-changing research findings to overcome real-world challenges. Jeff serves as the US Manager for Penetration Testing &amp;amp; Red Teaming at National Grid and as the CTO &amp;amp; Co-founder of ClaritySec, an Upstate New York based information security startup. Prior to this, he was the Director of Research for the Cyber Systems, Weapon Systems &amp;amp; Sensors Operation at Alion Science &amp;amp; Technology. In his spare time, Jeff enjoys experimenting with new blends of coffee, supporting local university’s information security programs, and participating in information security competitions, such as DEF CON Capture the Flag.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Today Jeff serves as technical adviser to the American Cybersecurity Institute and is a member of the SUNY Polytechnic Institute Cybersecurity Advisory Board, Mohawk Valley Community College Computer Science Advisory Board, (ISC)2 Central New York Chapter Board, and CNY Hackathon Competition Red Team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Find caffix here:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://twitter.com/jeff_foley Twitter]&lt;br /&gt;
&lt;br /&gt;
-- [https://github.com/caffix GitHub]&lt;br /&gt;
&lt;br /&gt;
-- [https://discord.gg/rtN8GMd Discord]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Artifacts:'''&lt;br /&gt;
&lt;br /&gt;
-- Bugcrowd LevelUp 0x04 Virtual Conference - &amp;quot;OWASP Amass: Discovering Internet Exposure&amp;quot; - [https://www.youtube.com/watch?v=C-GabM2db9A&amp;amp;list=PLIK9nm3mu-S6YoUjPrKtmBliUS4J5YOGl&amp;amp;index=3&amp;amp;t=0s Video]&lt;br /&gt;
&lt;br /&gt;
-- CSIAC Webinars - &amp;quot;OWASP Amass: Discovering Your Exposure on the Internet&amp;quot; - [https://www.youtube.com/watch?v=3jj7RjWYKm0&amp;amp;feature=youtu.be Video]&lt;br /&gt;
&lt;br /&gt;
-- &amp;quot;OWASP Amass: Beyond Subdomain Enumeration&amp;quot; talk at BSidesROC 2019 - [https://www.youtube.com/watch?v=ngOmkZ3U2e4 Video]&lt;br /&gt;
&lt;br /&gt;
-- OWASP Amass Project Showcase at AppSec USA 2018 - [https://www.youtube.com/watch?v=HaVEH1vFiN0&amp;amp;feature=youtu.be Video]&lt;br /&gt;
&lt;br /&gt;
-- Ligthning Talk (remote), &amp;quot;Introducing OWASP Amass Project&amp;quot; - [https://www.youtube.com/watch?v=8cOCaPwbr60 Video]&lt;br /&gt;
&lt;br /&gt;
-- Video of the 'Designing your Own Tools: The Amass Penetration Testing Tool' presentation at CNY Hackathon Fall 2017 - [https://www.youtube.com/watch?v=pCqxOk8Yq10 Video]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Project Lead and Developer to the following OWASP projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://www.owasp.org/index.php/OWASP_Amass_Project Amass DNS Enumeration and Network Mapping Tool Suite]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Additional Projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [http://www.cnyhackathon.org CNY Hackathon Competition]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=251995</id>
		<title>User:Caffix</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=251995"/>
				<updated>2019-05-30T21:54:22Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.linkedin.com/in/caffix https://www.owasp.org/images/7/7f/Linkedin-button.png]&lt;br /&gt;
[[File:Caffix_BSidesROC.jpeg|left|thumb]]&lt;br /&gt;
&lt;br /&gt;
Jeff Foley is an innovative, results-driven technical leader known for delivering game-changing research findings to overcome real-world challenges. Jeff serves as the US Manager for Penetration Testing &amp;amp; Red Teaming at National Grid and as the CTO &amp;amp; Co-founder of ClaritySec, an Upstate New York based information security startup. Prior to this, he was the Director of Research for the Cyber Systems, Weapon Systems &amp;amp; Sensors Operation at Alion Science &amp;amp; Technology. In his spare time, Jeff enjoys experimenting with new blends of coffee, supporting local university’s information security programs, and participating in information security competitions, such as DEF CON Capture the Flag.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Today Jeff serves as technical adviser to the American Cybersecurity Institute and is a member of the SUNY Polytechnic Institute Cybersecurity Advisory Board, Mohawk Valley Community College Computer Science Advisory Board, (ISC)2 Central New York Chapter Board, and CNY Hackathon Competition Red Team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Find caffix here:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://twitter.com/jeff_foley Twitter]&lt;br /&gt;
&lt;br /&gt;
-- [https://github.com/caffix GitHub]&lt;br /&gt;
&lt;br /&gt;
-- [https://discord.gg/rtN8GMd Discord]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Artifacts:'''&lt;br /&gt;
&lt;br /&gt;
-- CSIAC Webinars - &amp;quot;OWASP Amass: Discovering Your Exposure on the Internet&amp;quot; - [https://www.youtube.com/watch?v=3jj7RjWYKm0&amp;amp;feature=youtu.be Video]&lt;br /&gt;
&lt;br /&gt;
-- &amp;quot;OWASP Amass: Beyond Subdomain Enumeration&amp;quot; talk at BSidesROC 2019 - [https://www.youtube.com/watch?v=ngOmkZ3U2e4 Video]&lt;br /&gt;
&lt;br /&gt;
-- OWASP Amass Project Showcase at AppSec USA 2018 - [https://www.youtube.com/watch?v=HaVEH1vFiN0&amp;amp;feature=youtu.be Video]&lt;br /&gt;
&lt;br /&gt;
-- Ligthning Talk (remote), &amp;quot;Introducing OWASP Amass Project&amp;quot; - [https://www.youtube.com/watch?v=8cOCaPwbr60 Video]&lt;br /&gt;
&lt;br /&gt;
-- Video of the 'Designing your Own Tools: The Amass Penetration Testing Tool' presentation at CNY Hackathon Fall 2017 - [https://www.youtube.com/watch?v=pCqxOk8Yq10 Video]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Project Lead and Developer to the following OWASP projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://www.owasp.org/index.php/OWASP_Amass_Project Amass DNS Enumeration and Network Mapping Tool Suite]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Additional Projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [http://www.cnyhackathon.org CNY Hackathon Competition]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=251994</id>
		<title>User:Caffix</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=251994"/>
				<updated>2019-05-30T21:53:59Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.linkedin.com/in/caffix https://www.owasp.org/images/7/7f/Linkedin-button.png]&lt;br /&gt;
[[File:Caffix_BSidesROC.jpeg|left|thumb]]&lt;br /&gt;
&lt;br /&gt;
Jeff Foley is an innovative, results-driven technical leader known for delivering game-changing research findings to overcome real-world challenges. Jeff serves as the US Manager for Penetration Testing &amp;amp; Red Teaming at National Grid and as the CTO &amp;amp; Co-founder of ClaritySec, an Upstate New York based information security startup. Prior to this, he was the Director of Research for the Cyber Systems, Weapon Systems &amp;amp; Sensors Operation at Alion Science &amp;amp; Technology. In his spare time, Jeff enjoys experimenting with new blends of coffee, supporting local university’s information security programs, and participating in information security competitions, such as DEF CON Capture the Flag.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Today Jeff serves as technical adviser to the American Cybersecurity Institute and is a member of the SUNY Polytechnic Institute Cybersecurity Advisory Board, Mohawk Valley Community College Computer Science Advisory Board, (ISC)2 Central New York Chapter Board, and CNY Hackathon Competition Red Team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Find caffix here:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://twitter.com/jeff_foley Twitter]&lt;br /&gt;
&lt;br /&gt;
-- [https://github.com/caffix GitHub]&lt;br /&gt;
&lt;br /&gt;
-- [https://discord.gg/rtN8GMd Discord]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Artifacts:'''&lt;br /&gt;
&lt;br /&gt;
-- CSIAC Webinars - &amp;quot;OWASP Amass: Discovering Your Exposure on the Internet&amp;quot; - [https://www.youtube.com/watch?v=3jj7RjWYKm0&amp;amp;feature=youtu.be]&lt;br /&gt;
&lt;br /&gt;
-- &amp;quot;OWASP Amass: Beyond Subdomain Enumeration&amp;quot; talk at BSidesROC 2019 - [https://www.youtube.com/watch?v=ngOmkZ3U2e4 Video]&lt;br /&gt;
&lt;br /&gt;
-- OWASP Amass Project Showcase at AppSec USA 2018 - [https://www.youtube.com/watch?v=HaVEH1vFiN0&amp;amp;feature=youtu.be Video]&lt;br /&gt;
&lt;br /&gt;
-- Ligthning Talk (remote), &amp;quot;Introducing OWASP Amass Project&amp;quot; - [https://www.youtube.com/watch?v=8cOCaPwbr60 Video]&lt;br /&gt;
&lt;br /&gt;
-- Video of the 'Designing your Own Tools: The Amass Penetration Testing Tool' presentation at CNY Hackathon Fall 2017 - [https://www.youtube.com/watch?v=pCqxOk8Yq10 Video]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Project Lead and Developer to the following OWASP projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://www.owasp.org/index.php/OWASP_Amass_Project Amass DNS Enumeration and Network Mapping Tool Suite]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Additional Projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [http://www.cnyhackathon.org CNY Hackathon Competition]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=251403</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=251403"/>
				<updated>2019-05-11T22:07:34Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* OWASP Amass Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass project was originally created when the project leader 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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Lead:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=251402</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=251402"/>
				<updated>2019-05-11T22:07:19Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass project was originally created when the project leader 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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Lead:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping&lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=251401</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=251401"/>
				<updated>2019-05-11T21:50:50Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Roadmap */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass project was originally created when the project leader 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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Lead:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;January, 2019, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&lt;br /&gt;
* For version 3.0.0, update the user interfaces (UI) available&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Clean lists of DNS resolvers provided by users&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=251400</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=251400"/>
				<updated>2019-05-11T21:38:43Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* OWASP Amass Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
The OWASP Amass project was originally created when the project leader 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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Lead:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=251399</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=251399"/>
				<updated>2019-05-11T21:37:16Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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, querying public databases, recursive brute forcing, crawling web archives, permuting/altering DNS names, reverse DNS sweeping, and querying ASNs and netblocks associated with IP addresses. The information collected during an enumeration is used to build a graph database that maps an organization's presence on the Internet.&lt;br /&gt;
&lt;br /&gt;
When the enumeration is complete, an Amass 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.&lt;br /&gt;
&lt;br /&gt;
The software is implemented in the Go programming language, and 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 packages maintained by others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Lead:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=251311</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=251311"/>
				<updated>2019-05-10T12:18:27Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* News and Events */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [8 May 2019] Jeff Foley and Anthony Rhodes talked about Amass at the OWASP Rochester Chapter.&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Lead:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=250826</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=250826"/>
				<updated>2019-04-30T15:42:37Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Lead:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
* '''John Daniel Leon'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=250823</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=250823"/>
				<updated>2019-04-30T14:27:19Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* News and Events */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [1 May 2019] Jeff Foley talked about &amp;quot;Discovering Exposure on the Internet&amp;quot; on the CSIAC Webinar.&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Lead:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=250815</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=250815"/>
				<updated>2019-04-30T14:15:22Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Lead:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
* '''Semtex Oliviero'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Hauenstein'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=250159</id>
		<title>User:Caffix</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=250159"/>
				<updated>2019-04-15T19:55:50Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: Added a video link&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.linkedin.com/in/caffix https://www.owasp.org/images/7/7f/Linkedin-button.png]&lt;br /&gt;
[[File:Caffix_BSidesROC.jpeg|left|thumb]]&lt;br /&gt;
&lt;br /&gt;
Jeff Foley is an innovative, results-driven technical leader known for delivering game-changing research findings to overcome real-world challenges. Jeff serves as the US Manager for Penetration Testing &amp;amp; Red Teaming at National Grid and as the CTO &amp;amp; Co-founder of ClaritySec, an Upstate New York based information security startup. Prior to this, he was the Director of Research for the Cyber Systems, Weapon Systems &amp;amp; Sensors Operation at Alion Science &amp;amp; Technology. In his spare time, Jeff enjoys experimenting with new blends of coffee, supporting local university’s information security programs, and participating in information security competitions, such as DEF CON Capture the Flag.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Today Jeff serves as technical adviser to the American Cybersecurity Institute and is a member of the SUNY Polytechnic Institute Cybersecurity Advisory Board, Mohawk Valley Community College Computer Science Advisory Board, (ISC)2 Central New York Chapter Board, and CNY Hackathon Competition Red Team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Find caffix here:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://twitter.com/jeff_foley Twitter]&lt;br /&gt;
&lt;br /&gt;
-- [https://github.com/caffix GitHub]&lt;br /&gt;
&lt;br /&gt;
-- [https://discord.gg/rtN8GMd Discord]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Artifacts:'''&lt;br /&gt;
&lt;br /&gt;
-- &amp;quot;OWASP Amass: Beyond Subdomain Enumeration&amp;quot; talk at BSidesROC 2019 - [https://www.youtube.com/watch?v=ngOmkZ3U2e4 Video]&lt;br /&gt;
&lt;br /&gt;
-- OWASP Amass Project Showcase at AppSec USA 2018 - [https://www.youtube.com/watch?v=HaVEH1vFiN0&amp;amp;feature=youtu.be Video]&lt;br /&gt;
&lt;br /&gt;
-- Ligthning Talk (remote), &amp;quot;Introducing OWASP Amass Project&amp;quot; - [https://www.youtube.com/watch?v=8cOCaPwbr60 Video]&lt;br /&gt;
&lt;br /&gt;
-- Video of the 'Designing your Own Tools: The Amass Penetration Testing Tool' presentation at CNY Hackathon Fall 2017 - [https://www.youtube.com/watch?v=pCqxOk8Yq10 Video]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Project Lead and Developer to the following OWASP projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://www.owasp.org/index.php/OWASP_Amass_Project Amass DNS Enumeration and Network Mapping Tool Suite]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Additional Projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [http://www.cnyhackathon.org CNY Hackathon Competition]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=249955</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=249955"/>
				<updated>2019-04-10T20:42:51Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The Founder and Project Lead:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=249954</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=249954"/>
				<updated>2019-04-10T20:28:27Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributor to the project was:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additional contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
* '''Shane Ditton'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=249242</id>
		<title>User:Caffix</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=249242"/>
				<updated>2019-03-24T15:16:31Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.linkedin.com/in/caffix https://www.owasp.org/images/7/7f/Linkedin-button.png]&lt;br /&gt;
[[File:Caffix_BSidesROC.jpeg|left|thumb]]&lt;br /&gt;
&lt;br /&gt;
Jeff Foley is an innovative, results-driven technical leader known for delivering game-changing research findings to overcome real-world challenges. Jeff serves as the US Manager for Penetration Testing &amp;amp; Red Teaming at National Grid and as the CTO &amp;amp; Co-founder of ClaritySec, an Upstate New York based information security startup. Prior to this, he was the Director of Research for the Cyber Systems, Weapon Systems &amp;amp; Sensors Operation at Alion Science &amp;amp; Technology. In his spare time, Jeff enjoys experimenting with new blends of coffee, supporting local university’s information security programs, and participating in information security competitions, such as DEF CON Capture the Flag.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Today Jeff serves as technical adviser to the American Cybersecurity Institute and is a member of the SUNY Polytechnic Institute Cybersecurity Advisory Board, Mohawk Valley Community College Computer Science Advisory Board, (ISC)2 Central New York Chapter Board, and CNY Hackathon Competition Red Team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Find caffix here:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://twitter.com/jeff_foley Twitter]&lt;br /&gt;
&lt;br /&gt;
-- [https://github.com/caffix GitHub]&lt;br /&gt;
&lt;br /&gt;
-- [https://discord.gg/rtN8GMd Discord]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Artifacts:'''&lt;br /&gt;
&lt;br /&gt;
-- &amp;quot;OWASP Amass: Beyond Subdomain Enumeration&amp;quot; talk at BSidesROC - Video Pending&lt;br /&gt;
&lt;br /&gt;
-- OWASP Amass Project Showcase at AppSec USA 2018 - [https://www.youtube.com/watch?v=HaVEH1vFiN0&amp;amp;feature=youtu.be Video]&lt;br /&gt;
&lt;br /&gt;
-- Ligthning Talk (remote), &amp;quot;Introducing OWASP Amass Project&amp;quot; - [https://www.youtube.com/watch?v=8cOCaPwbr60 Video]&lt;br /&gt;
&lt;br /&gt;
-- Video of the 'Designing your Own Tools: The Amass Penetration Testing Tool' presentation at CNY Hackathon Fall 2017 - [https://www.youtube.com/watch?v=pCqxOk8Yq10 Video]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Project Lead and Developer to the following OWASP projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://www.owasp.org/index.php/OWASP_Amass_Project Amass DNS Enumeration and Network Mapping Tool Suite]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Additional Projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [http://www.cnyhackathon.org CNY Hackathon Competition]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=249241</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=249241"/>
				<updated>2019-03-24T15:14:05Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* News and Events */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributor to the project was:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additional contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=249240</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=249240"/>
				<updated>2019-03-24T15:13:40Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* News and Events */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [23 Mar 2019] Jeff Foley and Anthony Rhodes were talked about Amass at BSidesROC.&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributor to the project was:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additional contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=249239</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=249239"/>
				<updated>2019-03-24T15:10:50Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributor to the project was:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additional contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
* '''Daniel Martin'''&lt;br /&gt;
&lt;br /&gt;
* '''Benjamin Murray'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=247266</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=247266"/>
				<updated>2019-02-11T00:29:48Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* News and Events */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [8 Feb 2019] Adobe announced its integration of OWASP Amass with their Marinus project on Twitter.&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributor to the project was:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additional contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=246445</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=246445"/>
				<updated>2019-01-07T22:37:37Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributor to the project was:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additional contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
* '''Philip Drakopoulos'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=246140</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=246140"/>
				<updated>2018-12-18T22:44:07Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributor to the project was:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additional contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
* '''Adam Zinger'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245819</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245819"/>
				<updated>2018-12-06T15:54:05Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributor to the project was:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additional contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
* '''Anthony Rhodes'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245753</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245753"/>
				<updated>2018-12-05T15:27:53Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributor to the project was:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additional contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
* '''Randall Marsden'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245639</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245639"/>
				<updated>2018-11-29T05:18:49Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additional contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245638</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245638"/>
				<updated>2018-11-29T05:00:14Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* News and Events */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
The project has software deliverables that are implemented in the Go programming language. These deliverables include command-line tools, a local transform for [https://www.paterva.com/web7/buy/maltego-clients.php Maltego], 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 and the Snap package manager for Linux systems.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] OWASP Seattle Chapter meeting (hosted by T-Mobile) demonstration (remote) of the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additional contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245637</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245637"/>
				<updated>2018-11-29T04:48:58Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* News and Events */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
The project has software deliverables that are implemented in the Go programming language. These deliverables include command-line tools, a local transform for [https://www.paterva.com/web7/buy/maltego-clients.php Maltego], 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 and the Snap package manager for Linux systems.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [28 Nov 2018] Demonstrated the OWASP Amass project remotely at the OWASP Seattle Chapter meeting.&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter meeting (hosted by Facebook) lightning talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additional contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245322</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245322"/>
				<updated>2018-11-20T20:55:53Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
The project has software deliverables that are implemented in the Go programming language. These deliverables include command-line tools, a local transform for [https://www.paterva.com/web7/buy/maltego-clients.php Maltego], 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 and the Snap package manager for Linux systems.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter Meeting (Hosted by Facebook) Lightning Talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Additional contributors that have joined the project include:&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245321</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245321"/>
				<updated>2018-11-20T20:55:00Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
The project has software deliverables that are implemented in the Go programming language. These deliverables include command-line tools, a local transform for [https://www.paterva.com/web7/buy/maltego-clients.php Maltego], 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 and the Snap package manager for Linux systems.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter Meeting (Hosted by Facebook) Lightning Talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
* '''Wael Nasreddine'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245223</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=245223"/>
				<updated>2018-11-18T15:12:57Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: /* News and Events */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
The project has software deliverables that are implemented in the Go programming language. These deliverables include command-line tools, a local transform for [https://www.paterva.com/web7/buy/maltego-clients.php Maltego], 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 and the Snap package manager for Linux systems.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [18 Nov 2018] The Nix package manager added the OWASP Amass project to its package collection.&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter Meeting (Hosted by Facebook) Lightning Talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=244766</id>
		<title>User:Caffix</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=244766"/>
				<updated>2018-10-31T15:48:05Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.linkedin.com/in/caffix https://www.owasp.org/images/7/7f/Linkedin-button.png]&lt;br /&gt;
[[File:Caffix_BSidesROC.jpeg|left|thumb]]&lt;br /&gt;
&lt;br /&gt;
Jeff Foley is an innovative, results-driven technical leader known for delivering game-changing research findings to overcome real-world challenges. Jeff serves as the US Manager for Penetration Testing &amp;amp; Red Teaming at National Grid and as the CTO &amp;amp; Co-founder of ClaritySec, an Upstate New York based information security startup. Prior to this, he was the Director of Research for the Cyber Systems, Weapon Systems &amp;amp; Sensors Operation at Alion Science &amp;amp; Technology. In his spare time, Jeff enjoys experimenting with new blends of coffee, supporting local university’s information security programs, and participating in information security competitions, such as DEF CON Capture the Flag.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Today Jeff serves as technical adviser to the American Cybersecurity Institute and is a member of the SUNY Polytechnic Institute Cybersecurity Advisory Board, Mohawk Valley Community College Computer Science Advisory Board, (ISC)2 Central New York Chapter Board, and CNY Hackathon Competition Red Team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Find caffix here:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://twitter.com/jeff_foley Twitter]&lt;br /&gt;
&lt;br /&gt;
-- [https://github.com/caffix GitHub]&lt;br /&gt;
&lt;br /&gt;
-- [https://discord.gg/rtN8GMd Discord]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Artifacts:'''&lt;br /&gt;
&lt;br /&gt;
-- OWASP Amass Project Showcase at AppSec USA 2018 - [https://www.youtube.com/watch?v=HaVEH1vFiN0&amp;amp;feature=youtu.be Video]&lt;br /&gt;
&lt;br /&gt;
-- Ligthning Talk (remote), &amp;quot;Introducing OWASP Amass Project&amp;quot; - [https://www.youtube.com/watch?v=8cOCaPwbr60 Video]&lt;br /&gt;
&lt;br /&gt;
-- Video of the 'Designing your Own Tools: The Amass Penetration Testing Tool' presentation at CNY Hackathon Fall 2017 - [https://www.youtube.com/watch?v=pCqxOk8Yq10 Video]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Project Lead and Developer to the following OWASP projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://www.owasp.org/index.php/OWASP_Amass_Project Amass DNS Enumeration and Network Mapping Tool Suite]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Additional Projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [http://www.cnyhackathon.org CNY Hackathon Competition]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=244743</id>
		<title>User:Caffix</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=244743"/>
				<updated>2018-10-30T22:30:38Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.linkedin.com/in/caffix https://www.owasp.org/images/7/7f/Linkedin-button.png]&lt;br /&gt;
[[File:Caffix_BSidesROC.jpeg|left|thumb]]&lt;br /&gt;
&lt;br /&gt;
Jeff Foley is an innovative, results-driven technical leader known for delivering game-changing research findings to overcome real-world challenges. Jeff serves as the US Manager for Penetration Testing &amp;amp; Red Teaming at National Grid and as the CTO &amp;amp; Co-founder of ClaritySec, an Upstate New York based information security startup. Prior to this, he was the Director of Research for the Cyber Systems, Weapon Systems &amp;amp; Sensors Operation at Alion Science &amp;amp; Technology. In his spare time, Jeff enjoys experimenting with new blends of coffee, supporting local university’s information security programs, and participating in information security competitions, such as DEF CON Capture the Flag.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Today Jeff serves as technical adviser to the American Cybersecurity Institute and is a member of the SUNY Polytechnic Institute Cybersecurity Advisory Board, Mohawk Valley Community College Computer Science Advisory Board, (ISC)2 Central New York Chapter Board, and CNY Hackathon Competition Red Team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Find caffix here:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://twitter.com/jeff_foley Twitter]&lt;br /&gt;
&lt;br /&gt;
-- [https://github.com/caffix GitHub]&lt;br /&gt;
&lt;br /&gt;
-- [https://discord.gg/rtN8GMd Discord]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Artifacts:'''&lt;br /&gt;
&lt;br /&gt;
-- OWASP Amass Project Showcase at AppSec USA 2018 - [https://youtu.be/HaVEH1vFiN0 Video]&lt;br /&gt;
&lt;br /&gt;
-- Ligthning Talk (remote), &amp;quot;Introducing OWASP Amass Project&amp;quot; - [https://www.youtube.com/watch?v=8cOCaPwbr60 Video]&lt;br /&gt;
&lt;br /&gt;
-- Video of the 'Designing your Own Tools: The Amass Penetration Testing Tool' presentation at CNY Hackathon Fall 2017 - [https://www.youtube.com/watch?v=pCqxOk8Yq10 Video]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Project Lead and Developer to the following OWASP projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://www.owasp.org/index.php/OWASP_Amass_Project Amass DNS Enumeration and Network Mapping Tool Suite]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Additional Projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [http://www.cnyhackathon.org CNY Hackathon Competition]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=244739</id>
		<title>User:Caffix</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=244739"/>
				<updated>2018-10-30T18:43:12Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.linkedin.com/in/caffix https://www.owasp.org/images/7/7f/Linkedin-button.png]&lt;br /&gt;
[[File:Caffix_BSidesROC.jpeg|left|thumb]]&lt;br /&gt;
&lt;br /&gt;
Jeff Foley is an innovative, results-driven technical leader known for delivering game-changing research findings to overcome real-world challenges. Jeff serves as the US Manager for Penetration Testing &amp;amp; Red Teaming at National Grid and as the CTO &amp;amp; Co-founder of ClaritySec, an Upstate New York based information security startup. Prior to this, he was the Director of Research for the Cyber Systems, Weapon Systems &amp;amp; Sensors Operation at Alion Science &amp;amp; Technology. In his spare time, Jeff enjoys experimenting with new blends of coffee, supporting local university’s information security programs, and participating in information security competitions, such as DEF CON Capture the Flag.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Today Jeff serves as technical adviser to the American Cybersecurity Institute and is a member of the SUNY Polytechnic Institute Cybersecurity Advisory Board, Mohawk Valley Community College Computer Science Advisory Board, (ISC)2 Central New York Chapter Board, and CNY Hackathon Competition Red Team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Find caffix here:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://twitter.com/jeff_foley Twitter]&lt;br /&gt;
&lt;br /&gt;
-- [https://github.com/caffix GitHub]&lt;br /&gt;
&lt;br /&gt;
-- [https://discord.gg/rtN8GMd Discord]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Artifacts:'''&lt;br /&gt;
&lt;br /&gt;
-- OWASP Amass Project Showcase - [https://youtu.be/HaVEH1vFiN0 Video]&lt;br /&gt;
&lt;br /&gt;
-- Ligthning Talk (remote), &amp;quot;Introducing OWASP Amass Project&amp;quot; - [https://www.youtube.com/watch?v=8cOCaPwbr60 Video]&lt;br /&gt;
&lt;br /&gt;
-- Video of the 'Designing your Own Tools: The Amass Penetration Testing Tool' presentation at CNY Hackathon Fall 2017 - [https://www.youtube.com/watch?v=pCqxOk8Yq10 Video]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Project Lead and Developer to the following OWASP projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://www.owasp.org/index.php/OWASP_Amass_Project Amass DNS Enumeration and Network Mapping Tool Suite]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Additional Projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [http://www.cnyhackathon.org CNY Hackathon Competition]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=244390</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=244390"/>
				<updated>2018-10-19T14:20:08Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
The project has software deliverables that are implemented in the Go programming language. These deliverables include command-line tools, a local transform for [https://www.paterva.com/web7/buy/maltego-clients.php Maltego], 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 and the Snap package manager for Linux systems.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter Meeting (Hosted by Facebook) Lightning Talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in the project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer. The project needs different skills and expertise at different times during its development. Currently, we are looking for researchers, programmers, writers, and graphic designers.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=244366</id>
		<title>OWASP Amass Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Amass_Project&amp;diff=244366"/>
				<updated>2018-10-18T22:32:00Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==OWASP Amass Project==&lt;br /&gt;
&lt;br /&gt;
In-depth DNS Enumeration and Network Mapping written in Go!&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If users wish to maintain the information collected by the Amass software, data handlers interface with storage systems, such as [https://neo4j.com/ Neo4j]. Additional handlers can easily be implemented in order to support other databases or even custom solutions.&lt;br /&gt;
&lt;br /&gt;
The project has software deliverables that are implemented in the Go programming language. These deliverables include command-line tools, a local transform for [https://www.paterva.com/web7/buy/maltego-clients.php Maltego], 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 and the Snap package manager for Linux systems.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
This program is free software: you can redistribute it and/or modify it under the terms of the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0] license.  OWASP Amass and any contributions are Copyright &amp;amp;copy; by Jeff Foley 2017.  &lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass Source Code]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/releases What's New (Revision History)]]&lt;br /&gt;
&lt;br /&gt;
[[Https://github.com/OWASP/Amass/issues Issue Tracker]]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
[https://www.owasp.org/index.php/User:Caffix Jeff Foley]&lt;br /&gt;
&lt;br /&gt;
  {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;1&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; | [[File:All_your_systems2.png]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
* [18 Oct 2018] DragonFly BSD added the OWASP Amass project to DPorts package management.&lt;br /&gt;
&lt;br /&gt;
* [12 Oct 2018] OWASP showcased the Amass project at AppSec USA 2018.&lt;br /&gt;
&lt;br /&gt;
* [11 Sep 2018] FreeBSD added the OWASP Amass project to the Ports package collection.&lt;br /&gt;
&lt;br /&gt;
* [10 Sep 2018] OWASP Amass project was added to the Arch Linux User Repository (AUR).&lt;br /&gt;
&lt;br /&gt;
* [6 Sep 2018] OWASP London Chapter Meeting (Hosted by Facebook) Lightning Talk (remote) to introduce the OWASP Amass project.&lt;br /&gt;
&lt;br /&gt;
* [4 Jul 2018] OWASP announced acceptance of the Amass project on Twitter.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==How can I participate in your project?==&lt;br /&gt;
&lt;br /&gt;
All you have to do is make the Project Leader aware of your available time to [https://github.com/OWASP/Amass/blob/master/CONTRIBUTING.md contribute to the project]. It is also important to let the leader know how you would like to contribute and pitch in to help the project meet its goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leader is key. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in your project?==&lt;br /&gt;
&lt;br /&gt;
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.   See the Road Map and Getting Involved tab for more details.&lt;br /&gt;
&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
&lt;br /&gt;
* '''Jeff Foley'''&lt;br /&gt;
&lt;br /&gt;
* '''Mikail Tunç'''&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;July, 2018, the highest priorities for the next 12 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
* Feature enhancement: Allow Amass to connect to proxies&lt;br /&gt;
* Feature enhancement: Inform users of what Amass will do once an enumeration is executed&lt;br /&gt;
* Feature enhancement: Add additional constraints to the enumeration process&lt;br /&gt;
* Continue to update data sources that provide DNS names&lt;br /&gt;
* Implement additional data handlers that save information gathered into various data stores&lt;br /&gt;
* Implement documentation regarding Amass architecture and the enumeration process&lt;br /&gt;
* Develop slides and videos to serve as demonstration material&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can support the OWASP Amass project. Below are some of the roles that definitely need additional support:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if some Go network programmers wanted to join the project.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
Amass leverages concurrency and produces quite a bit of network traffic, which can always use additional testing. Anyone interested in stressing the software and helping to improve its quality is welcome.&lt;br /&gt;
&lt;br /&gt;
===Writing===&lt;br /&gt;
&lt;br /&gt;
The project could currently use technical writers to join the team in order to capture how the software works.&lt;br /&gt;
=Project About=&lt;br /&gt;
{{Template:Project About&lt;br /&gt;
| project_name =OWASP Amass&lt;br /&gt;
| project_description = In-depth DNS Enumeration and Network Mapping written in Go &lt;br /&gt;
| project_license = Apache License 2.0&lt;br /&gt;
| leader_name1 = Jeff Foley&lt;br /&gt;
| leader_email1 = jeff.foley@owasp.org&lt;br /&gt;
| leader_username1 = caffix&lt;br /&gt;
| mailing_list_name =&lt;br /&gt;
}}  &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=243840</id>
		<title>User:Caffix</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=243840"/>
				<updated>2018-09-29T20:50:42Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.linkedin.com/in/caffix https://www.owasp.org/images/7/7f/Linkedin-button.png]&lt;br /&gt;
[[File:Caffix_BSidesROC.jpeg|left|thumb]]&lt;br /&gt;
&lt;br /&gt;
Jeff Foley is an innovative, results-driven technical leader known for delivering game-changing research findings to overcome real-world challenges. Jeff serves as the US Manager for Penetration Testing &amp;amp; Red Teaming at National Grid and as the CTO &amp;amp; Co-founder of ClaritySec, an Upstate New York based information security startup. Prior to this, he was the Director of Research for the Cyber Systems, Weapon Systems &amp;amp; Sensors Operation at Alion Science &amp;amp; Technology. In his spare time, Jeff enjoys experimenting with new blends of coffee, supporting local university’s information security programs, and participating in information security competitions, such as DEF CON Capture the Flag.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Today Jeff serves as technical adviser to the American Cybersecurity Institute and is a member of the SUNY Polytechnic Institute Cybersecurity Advisory Board, Mohawk Valley Community College Computer Science Advisory Board, (ISC)2 Central New York Chapter Board, and CNY Hackathon Competition Red Team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Find caffix here:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://twitter.com/jeff_foley Twitter]&lt;br /&gt;
&lt;br /&gt;
-- [https://github.com/caffix GitHub]&lt;br /&gt;
&lt;br /&gt;
-- [https://discord.gg/rtN8GMd Discord]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Artifacts:'''&lt;br /&gt;
&lt;br /&gt;
-- Ligthning Talk (remote), &amp;quot;Introducing OWASP Amass Project&amp;quot; - [https://www.youtube.com/watch?v=8cOCaPwbr60 Video]&lt;br /&gt;
&lt;br /&gt;
-- Video of the 'Designing your Own Tools: The Amass Penetration Testing Tool' presentation at CNY Hackathon Fall 2017 - [https://www.youtube.com/watch?v=pCqxOk8Yq10 Video]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Project Lead and Developer to the following OWASP projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://www.owasp.org/index.php/OWASP_Amass_Project Amass DNS Enumeration and Network Mapping Tool Suite]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Additional Projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [http://www.cnyhackathon.org CNY Hackathon Competition]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=243839</id>
		<title>User:Caffix</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Caffix&amp;diff=243839"/>
				<updated>2018-09-29T20:39:24Z</updated>
		
		<summary type="html">&lt;p&gt;Caffix: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.linkedin.com/in/caffix https://www.owasp.org/images/7/7f/Linkedin-button.png]&lt;br /&gt;
[[File:Caffix_BSidesROC.jpeg|left|thumb]]&lt;br /&gt;
&lt;br /&gt;
Jeff Foley is an innovative, results-driven technical leader known for delivering game-changing research findings to overcome real-world challenges. Jeff serves as the US Manager for Penetration Testing &amp;amp; Red Teaming at National Grid and as the CTO &amp;amp; Co-founder of ClaritySec, an Upstate New York based information security startup. Prior to this, he was the Director of Research for the Cyber Systems, Weapon Systems &amp;amp; Sensors Operation at Alion Science &amp;amp; Technology. In his spare time, Jeff enjoys experimenting with new blends of coffee, supporting local university’s information security programs, and participating in information security competitions, such as DEF CON Capture the Flag.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Today Jeff participates as technical adviser for the American Cybersecurity Institute and is a member of the SUNY Polytechnic Institute Cybersecurity Advisory Board, Mohawk Valley Community College Computer Science Advisory Board, (ISC)2 Central New York Chapter Board, and CNY Hackathon Competition Red Team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Find caffix here:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://twitter.com/jeff_foley Twitter]&lt;br /&gt;
&lt;br /&gt;
-- [https://github.com/caffix GitHub]&lt;br /&gt;
&lt;br /&gt;
-- [https://discord.gg/rtN8GMd Discord]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Artifacts:'''&lt;br /&gt;
&lt;br /&gt;
-- Ligthning Talk (remote), &amp;quot;Introducing OWASP Amass Project&amp;quot; - [https://www.youtube.com/watch?v=8cOCaPwbr60 Video]&lt;br /&gt;
&lt;br /&gt;
-- Video of the 'Designing your Own Tools: The Amass Penetration Testing Tool' presentation at CNY Hackathon Fall 2017 - [https://www.youtube.com/watch?v=pCqxOk8Yq10 Video]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Project Lead and Developer to the following OWASP projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [https://www.owasp.org/index.php/OWASP_Amass_Project Amass DNS Enumeration and Network Mapping Tool Suite]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Additional Projects:'''&lt;br /&gt;
&lt;br /&gt;
-- [http://www.cnyhackathon.org CNY Hackathon Competition]&lt;/div&gt;</summary>
		<author><name>Caffix</name></author>	</entry>

	</feed>