Skip to content
This repository has been archived by the owner on Sep 20, 2023. It is now read-only.

Commit

Permalink
Browse files Browse the repository at this point in the history
  • Loading branch information
1earch authored and nadouani committed Dec 9, 2019
1 parent 751e6b5 commit 5b7aa53
Showing 1 changed file with 8 additions and 1 deletion.
9 changes: 8 additions & 1 deletion analyzer_requirements.md
Original file line number Diff line number Diff line change
Expand Up @@ -186,6 +186,13 @@ for more information on setting it up.
To configure the analyzer you need to supply the **API URL** of your local instance
as a value of the `url` parameter.

In addition, since Cuckoo 2.0.7, you need to specify an **API token** used for authentication.
This token can be found in your configuration, in the Cuckoo Working Directory (`$CWD/conf/cuckoo.conf`).

Finally, if you secured your API calls thanks to HTTPS, using a custom CA, you can specify it in
the `cert_path` parameter (`/etc/ssl/certs/my-custom-ca.pem`). Alternatively, you can disable TLS
certificate verification setting the `cert_check` parameter to false.

### Cybercrime-Tracker
Use the [Cybercrime-tracker.net](http://cybercrime-tracker.net/) service to assess whether an IP address, URL, domain, or FQDN has a C2 (Command & Control) entry in its database.

Expand Down Expand Up @@ -1058,4 +1065,4 @@ Add domain from observables in cases to Umbrella blacklist.

#### Requirements

To configure the responder, provide the url of the service as a value for the `integration_url` parameter.
To configure the responder, provide the url of the service as a value for the `integration_url` parameter.

0 comments on commit 5b7aa53

Please sign in to comment.