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

Update doc to support Cuckoo 2.0.7 and custom CA #38

Merged
merged 1 commit into from
Dec 9, 2019
Merged

Update doc to support Cuckoo 2.0.7 and custom CA #38

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion analyzer_requirements.md
View file
Open in desktop
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.