|Number of watchers on Github||64|
|Number of open issues||5|
|Average time to merge a PR||about 4 hours|
|Open pull requests||0+|
|Closed pull requests||0+|
|Last commit||over 2 years ago|
|Repo Created||over 3 years ago|
|Repo Last Updated||over 1 year ago|
|Organization / Author||yelp|
|Do you use amira? Leave a review!|
|View open issues (5)|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
AMIRA is a service for automatically running the analysis on the OSXCollector output files. The automated analysis is performed via OSXCollector Output Filters, in particular The One Filter to Rule Them All: the Analyze Filter. AMIRA takes care of retrieving the output files from an S3 bucket, running the Analyze Filter and then uploading the results of the analysis back to S3 (although one could envision as well attaching them to the related JIRA ticket).
The following steps assume you have tox installed on your machine.
If this is not the case, please run:
$ sudo pip install tox
AMIRA uses OSXCollector Output Filters to do the actual analysis,
so you will need to have a valid
configuration file in the working directory.
The example configuration file can be found in the
OSXCollector Output Filters.
The configuration file mentions the location of the file hash and the domain blacklists. Make sure that the blacklist locations mentioned in the configuration file are also available when running AMIRA.
AMIRA uses boto to interface with AWS. You can supply the credentials using either of the possible boto config files.
The credentials should allow reading and deleting SQS messages from the SQS queue specified in the AMIRA config as well as the read access to the objects in the S3 bucket where the OSXCollector output files are stored. To be able to upload the analysis results back to the S3 bucket specified in the AMIRA configuration file, the credentials should also allow write access to this bucket.
The service uses the
S3 bucket event notifications
to trigger the analysis.
You will need to configure an S3 bucket for the OSXCollector output files,
so that when a file is added there the notification will be sent to an SQS queue
AmiraS3EventNotifications in the picture below).
AMIRA periodically checks the queue for any new messages
and upon receiving one it will fetch the OSXCollector output file from the S3
It will then run the Analyze Filter on the retrieved file.
The Analyze Filter runs all the filters contained in the OSXCollector Output Filters package sequentially. Some of them communicate with the external resources, like domain and hashes blacklists (or whitelists) and threat intel APIs, e.g. VirusTotal, OpenDNS Investigate or ShadowServer. The original OSXCollector output is extended with all of this information and the very last filter run by the Analyze Filter summarizes all of the findings into a human-readable form. After the filter finishes running, the results of the analysis will be uploaded to the Analysis Results S3 bucket.
The overview of the whole process and the system components involved in it are depicted below:
The main entry point to AMIRA is in the
You will first need to create an instance of AMIRA class by providing the AWS
region name, where the SQS queue with the event notifications for the
OSXCollector output bucket is, and the SQS queue name:
from amira.amira import AMIRA amira = AMIRA('us-west-1', 'AmiraS3EventNotifications')
Then you can register the analysis results uploader, e.g. the S3 results uploader:
from amira.s3 import S3ResultsUploader s3_results_uploader = S3ResultsUploader('amira-results-bucket') amira.register_results_uploader(s3_results_uploader)
Finally, run AMIRA:
Go get some coffee, sit back, relax and wait till the analysis results pop up in the S3 bucket!