2.2.7. Team-Only Settings
This section covers settings that are only relevant to Team deployments.
2.2.7.1. Server Accessible Data Source Folder
You can configure your server to know about a folder that investigators can copy data into and then process. For example:
A folder that is local to the server, but that is shared so that investigators can copy data into it.
A folder on a network share that investigators copoy data into.
This feature makes it easier for investigators to add data into an incident:
Web browser clients cannot process disk or memory images. But, if the disk or memory image is in this folder, then the investigator can point the server at them to process.
Both types of clients will upload JSON data to a server to be processed. If the data is already in this folder, no upload is required.
Enable this setting in the “Team Settings” section of the Options panel.
Once this is configured, then many of the “Add Host” methods will have a Server Accessible option enabled (see Collector Output).
If it is not enabled, the Disk Image and Cyber Triage File dialogs will show “Server accessible data sources are disabled. An administrator can enable them in Options > Team Settings.”
2.2.7.2. Allow Collector To Initiate Ingests
By default, the Cyber Triage Server accepts connections from the Collector when initiated from an “Add Host” wizard. The Team Server can be configured to always accept connections, as long as it has a “secret key”.
This feature is useful when deploying the Collector via EDR or other IT infrastructure.
To enable this feature, go to the “Team Settings” section of the options panel and enable “Allow collections to be automatically created by Collector”.
Choose the default malware scan settings and record the “key” and “cert_hash”. You’ll need that when you start the collections.
Refer to Launch via EDR for steps on launching the Collector.
2.2.7.3. REST API Access
Note
This feature requires an Enterprise-tier license.
The Server has a REST API on port 9443 that clients and other web services can connect to. The specification can be found at REST API Reference.
You can enable it in the “Team Settings” options panel.
2.2.7.4. Incident-Level Access Control
This feature allows you to control which users have access to an incident.
Note
This feature requires an Enterprise-tier license.
To use this feature, you must enable it from the Options panel, under “Users and Permissions” / “Incident Access Control”.
You have three options:
Enable Incident-level Access Control Enable this if you want to restrict access to incidents.
Force all new incidents to be restricted Enable this if you want every incident to start of restricted.
Allow incidents without restrictions to be used for analysis of other hosts and baselines Enable this to allow unrestricted hosts to be added to the central database for correlation and baselining. Restricted hosts are never added to this database. Law enforcement groups that are concerned about using data from past cases may disable this feature.
After you have enabled this, then make sure to also review:
2.2.7.5. Maximum Concurrent Ingests
The Team Server limits how many ingests can run at the same time. This can be configured, up to the limit allowed by your license, from the System / “Team Settings” section of the options panel.
2.2.7.6. Team Server Status
You can get basic status of the Cyber Triage Server by pointing a web browser at: https://SERVER_HOST_NAME:9443/api/admin/service-status