If you wish to deploy in AWS, use this previous release.

Concrete Relay implementation using SecurityTrails as a third-party Cyber Threat Intelligence service provider.

The Relay itself is just a simple application written in Python that can be easily packaged and deployed. This relay is now Cisco Hosted and no longer requires AWS Lambda.

• We need an application that will translate API requests from SecureX Threat Response to the third-party integration, and vice versa.
• We need an application that can be completely self contained within a virtualized container using Docker.

If you want to test the application you have to install a couple of extra dependencies from the test-requirements.txt file:

pip install --upgrade --requirement requirements.txt

You can perform two kinds of testing:

• Run static code analysis checking for any semantic discrepancies and PEP 8 compliance:

  flake8 .

• Run the suite of unit tests and measure the code coverage:

  coverage run --source api/ -m pytest --verbose tests/unit/ && coverage report

NOTE. If you need input data for testing purposes you can use data from the observables.json file.

In order to build the application, we need to use a Dockerfile.

1. Open a terminal. Build the container image using the docker build command.

docker build -t tr-05-securitytrails .

2. Once the container is built, and an image is successfully created, start your container using the docker run command and specify the name of the image we have just created. By default, the container will listen for HTTP requests using port 9090.

docker run -dp 9090:9090 --name tr-05-securitytrails tr-05-securitytrails

3. Watch the container logs to ensure it starts correctly.

docker logs tr-05-securitytrails

4. Once the container has started correctly, open your web browser to http://localhost:9090. You should see a response from the container.

curl http://localhost:9090

• POST /health

  • Verifies the Authorization Bearer JWT and decodes it to restore the original credentials.
  • Authenticates to the underlying external service to check that the provided credentials are valid and the service is available at the moment.

• POST /observe/observables

  • Accepts a list of observables and filters out unsupported ones.
  • Verifies the Authorization Bearer JWT and decodes it to restore the original credentials.
  • Makes a series of requests to the underlying external service to query for some cyber threat intelligence data on each supported observable.
  • Maps the fetched data into appropriate CTIM entities.
  • Returns a list per each of the following CTIM entities (if any extracted):
    • Sighting.

• POST /refer/observables

  • Accepts a list of observables and filters out unsupported ones.
  • Builds a search link per each supported observable to pivot back to the underlying external service and look up the observable there.
  • Returns a list of those links.

• POST /version

  • Returns the current version of the application.

• ip
• ipv6
• domain

Each SecurityTrails response generates a single CTIM Sighting.

• The time of investigation is used as a Sighting.observed_time.start_time.

• If an investigated observable is an IP/IPv6:

  • a request to the SecurityTrails Domains - Search Endpoint is done.
  • unique values from the .records[].values[].ip/.records[].values[].ipv4 field are linked as Sighting observed relations domain->'Resolved_To'->IP/IPv6.
  • the record_count field is used as a Sighting.count.

• If an investigated observable is a domain:

  • two requests to the SecurityTrails History - DNS Endpoint are done (to get IP and IPv6 addresses domain resolves to).
  • unique values from the .records[].values[].ip/.records[].values[].ipv4 field are linked as Sighting observed relations domain->'Resolved_To'->IP/IPv6.
  • the number of unique IP/IPv6 domain resolves to is used as a Sighting.count.