Evidence Repositories
Where to save your collected data
By default, AIR supports saving collected evidence locally on the asset with paths set as Binalyze\AIR for Windows, /opt/binalyze/air for Linux, and /opt/binalyze/air for macOS. Alternatively, users can opt to send their collections to Evidence Repositories such as network shares; SMB, FTPS, SFTP, or to cloud storage; AWS S3 Buckets and Azure Blob Storage.
Defining exact system resource requirements for the Evidence Repository is challenging due to variations in environments, asset counts, and the types of acquisition tasks performed. Disk space, CPU, and memory needs can vary widely, influenced by factors like the size of disk images, log files collected during acquisitions, and the volume of evidence gathered from each asset. As a result, it’s impractical to offer a one-size-fits-all recommendation for resource allocation.
The term Evidence Repository describes a remote location, off the actual asset subject to the tasking assignment, whether it is any one of the 5 currently supported storage options.
You can create Evidence Repositories in three different ways:
From the “Evidence Repositories” page
During Policy creation
During Acquisition task creation
A common query from our customers revolves around the configuration of the Evidence Repository and how it interacts with the AIR Console, especially concerning evidence uploads and the necessary network permissions. Here's what you need to know:
Evidence Upload Process
When configuring the Evidence Repository, it's essential to understand the pathway through which evidence files are uploaded. Specifically, there might be confusion about whether these uploads occur directly from the assets to the Evidence Repository or if they go through the AIR console.
To clarify: Evidence files are uploaded directly from the assets to the Evidence Repository. This process necessitates configuring your firewall to permit traffic from the asset to the Evidence Repository on the relevant ports. For example, if using SMB for evidence transfer, you must allow access through port 445.
AIR Console Access
For the File Explorer feature within the AIR console to function correctly, the AIR console requires access to the Evidence Repository. This setup ensures that users can seamlessly browse and interact with the stored evidence directly through the AIR console interface.
Configuring Your Firewall
Given these operational details, it's necessary to adjust your firewall settings accordingly:
Allow traffic from your assets to the Evidence Repository, particularly if using specific protocols like SMB on port 445.
Ensure the AIR Console has access to the Evidence Repository to enable full functionality of the File Explorer feature.
Creating evidence repository from “Evidence Repositories”
1. Navigate to the Evidence Repositories section by clicking the Settings button in the Main Menu button and then select “Evidence Repositories” from the Secondary Menu.
2. Click the “+Add New” button on the top of the page.
3. From the New Evidence Repository window, provide a name to the repository and then select the relevant repository.
4. Depending on the type of evidence repository you choose, the required fields are adjusted accordingly:
SMB
Path: The location that is polled for evidence. If the IP address of the repository is "172.16.1.1", and the folder name is "Share", the path will be “\\172.16. 1.1\Share” without quotes.
Username (if required)
Password (if required)
SFTP
Host: Hostname or IP address of the SFTP server.
Port: The port on which the SFTP server is listening to. The default port for SFTP is 22.
Path: The location directory that is polled for evidence.
Username (if required)
Password (if required)
FTPS
Host: Hostname or IP address of the FTPS server.
Port: The port on which the FTPS server is listening to. The default port for FTPS is 21.
Path: The location directory that is polled for evidence.
Username (if required)
Password (if required)
NB: Implicit SSL/TLS is not supported
Amazon S3
Region: Region name for the bucket that was created in.
Bucket: Name of the bucket
Access Key ID
Secret Access Key
Note: IAM users must have proper rights and permissions to access the S3 bucket.
Azure Blob
Shared Access Signature (SAS) URL See https://docs.microsoft.com/en-us/azure/storage/common/storage-sas-overview for details.
Creating evidence repository during Policy creation
1. Select the Settings button in the Main Menu button and then select “Policies” from the Secondary Menu.
Click the “+Add New” button on the top of the page
2. Provide a name to the repository and then select the relevant repository type:
3. Select the relevant repository type by clicking on it.
4. Click the “Save” button.
5. The newly created repository will appear in the drop-down list, select the relevant repository and finalize the process.
Creating evidence repository during acquisition task creation
1. From the “Acquire Evidence” pane, click on the Evidence Repository radio button under the "Save Collected Evidence To" section.
2. Click in the "Repository" box“ and then select “+ Add new repository”:
3. From the window 'New Repository' complete the mandatory fields and select the type of repository you with to add there are five options:
SMB
SFTP
FTPS
Amazon S3
Azure Blob
4. The newly created repository will appear in the drop-down list, select the repository you want for this particular acquisition and finalize your Acquisition Task via the wizard.
To improve task reliability and prevent failed uploads, a connection check for evidence repositories will take place when starting acquisition tasks (both scheduled and immediate). Here's how it works:
When creating tasks like Acquisition or Acquire Image, AIR automatically checks the connection to the selected repository (SFTP, FTPS, Azure, or AWS).
If the connection check takes longer than 10 seconds, it will be canceled, and a warning message will appear. However, task creation is not blocked—you can choose to proceed or cancel the task if the repository is inaccessible.
UI Warning Message: If the repository is inaccessible, you'll see this warning: "The following evidence repositories are currently inaccessible. If responders cannot access these repositories, they will not be able to send the collected evidence. Please note that access to these repositories is managed through the AIR server. If the responders have access, evidence transmission will proceed without issues. Do you still want to continue?"
This feature ensures you're aware of potential access issues before initiating a task, helping you avoid wasted time on failed uploads. It’s important to note that this connection check occurs between the AIR console and the repository—not between the responders and the repository. While it's impractical to check every responder in large-scale tasks, a successful console check significantly reduces the likelihood of connection issues for responders.
Last updated
