To get started with intrigue-core using Docker, you’ll need to install Docker on your machine.

Next, pull down the intrigue-core repository to your local machine with a git clone and jump into the directory:

$ git clone
$ cd intrigue-core

Then use Docker to build an image:

$ docker build .

Finally, (this is pretty easy, huh?) run the image with Docker!

$ docker run -i -t -p [image id]

This will start the docker image with the intrigue-core services, giving you output that looks like the following (shortened for brevity):

Starting PostgreSQL 9.6 database server                                                                                                                                                           [ OK ] 
Starting redis-server: redis-server.
Starting intrigue-core processes
[+] Setup initiated!
[+] Generating system password: hwphqlymmpfrqurv
[+] Copying puma config....
[ ] File already exists, skipping: /core/config/puma.rb

* Listening on tcp://
Use Ctrl-C to stop

As it starts up, you can see that it generates a unique password. You can  now log in with the username intrigue and the password above at http://localhost:7777 on your host machine!

Now, you’re up and running,  see: Up and running with Intrigue-core

UPDATE: The latest test image can be found by searching ‘intrigue-core-latest’ in Community AMIs. It is currently only available in the Northern Virginia (US-east-1) region on EC2.

I’ve made an EC2 instance available for testing if you’d like a simple way to try it out. Here’s a simple demo of how to get started.

The current AMI name is: intrigue-core-latest-20190218 and the ID is: intrigue-core-latest-20190218

Once it’s up & running, update by logging in and running:

$ cd core && git pull && bundle install && ./util/control restart

Congrats, you’re up and running. Access the interface at http://%5Bhostname%5D:7777.

Intelligence Gathering, Reconnaissance, Targeting, or Pre-Collection… No matter what you call it, it’s an important component of any security assessment project.

Intelligence Gathering:  The collection of intelligence both overt and covert to aid in the decision of a course of action.

Intelligence Gathering (IG) is often viewed and approached as the first step of an assessment project. A penetration tester will diligently scan the target’s website, gather DNS information, check Google for email addresses and they might even check SHODAN for exploitable hosts.

Unfortunately, this is often where the Intelligence Gathering stops. The assessor now has enough information to move on to the “Active Scanning” or “Exploitation” phases, suddenly ignoring that they will need to continuously perform IG on new information throughout an assessment.

… So what is is Intelligence Gathering at it’s core? There are a number of recognized disciplines within the scope of Intelligence Gathering. The most recognizable of these is Open Source Intelligence (OSINT), or intelligence gathering performed on publicly available sources. In the Intelligence Community (IC), the term “open” refers to overt, publicly available sources (as opposed to covert or clandestine sources);

We often focus on OSINT, but there are others such as SIGINT and HUMINT that are often left untouched when assessing security of an entity since they may not be relevant, in scope, or within the control of the entity that commissioned the assessment.

The process can be difficult to scope – until you’ve gained enough information to capture your goal, you’ll continue to gather intelligence and analyze it, filtering it into a model of the target. “Enough” IG largely depends on the goals of the application for which its used. If you’ve not been successful at gaining your target, then you have more to do.

Performing Intelligence Gathering at scale can also be challenging. A small business or organization can consist of thousands of entities which may, or may not be relevant during an assessment. An enterprise, made up of thousands, if not millions of entities and the relationships between them is simply mind-boggling and impossible to process with traditional techniques. This is truly a “big data” problem.

Our mission is to make Intelligence Gathering and Analysis simple, and support the assessment efforts of security professionals.