YaraGuardian

A django web interface for managing Yara rules. The manager enables users to:

* Search for specific rules based on rule characteristics
* Categorize and organize rules easily and in bulk
* Make bulk edits on desired/filtered rules
* Track characteristics of the entire rule repository
* Automatically prevent and detect duplicate entries

Rule Stats Summary

Get stats data on the entire rule repository

Rule Search Form

Search, manage, and export rules matching specific criteria

Rule Search Results

View and perform in-place edits on search results

Rule Edit Form

Modify or update a large set of rules based on various characteristics

Installation and Configuration Instructions (Development environment)

Base django application requirements can be installed via vagrantfile or install.sh
- Be sure to review install.sh beforehand as it contains default configs for psql
Settings are specified either via ENV variables or the config.json file
- Any ENV variables specified will override values that are present in the config.json file
Activate python environment
- pipenv shell
Use the Django manage.py to create initial tables and superuser
- python manage.py migrate
- python manage.py createsuperuser
Collect static files
- python manage.py collectstatic
Run the server
- python manage.py runserver 0.0.0.0:8000 -OR- gunicorn YaraGuardian.wsgi --bind=0.0.0.0:8000
- make sure to set SERVE_STATIC=True if DEBUG=False and you are not using another method for static file serving like Nginx

Installation and Configuration Instructions (Docker Example)

Build the image
- docker build .
Prepare static files
- docker-compose run web yarn
- docker-compose run web yarn webpack
- docker-compose run web python3 /usr/local/YaraGuardian/manage.py collectstatic --noinput
Perform DB Migrations and Create initial user
- docker-compose run web python3 /usr/local/YaraGuardian/manage.py migrate
- docker-compose run web python3 /usr/local/YaraGuardian/manage.py createsuperuser
Run YaraGuardian
- docker-compose up

Configurable settings

The following are the available configurable settings to be specified via environment variables or the config.json file:

SECRET_KEY
- Required
DATABASE_NAME
- Required
DATABASE_USER
- Required
DATABASE_PASS
- Required
DATABASE_HOST
- Optional, defaults to '127.0.0.1'
DATABASE_PORT
- Optional, defaults to '5432'
DEBUG
- Optional, defaults to 'False'
- WARNING: This will cause email settings to be ignored and redirect email output to console
ALLOWED_HOSTS
- Optional, defaults to []
GUEST_REGISTRATION
- Optional, defaults to 'DISABLED'
EMAIL_HOST
- SMTP server authentication host
- Optional, defaults to 'smtp.gmail.com'
EMAIL_PORT
- SMTP server authentication port
- Optional, defaults to '587'
EMAIL_USER
- SMTP server authentication username
- Required if not in Debug mode
EMAIL_PASSWORD
- SMTP server authentication password
- Required if not in Debug mode
EMAIL_USE_TLS
- SMTP server authentication TLS enforced
- Optional, defaults to 'True'
EMAIL_SSL_CERTFILE
- Path to a PEM-formatted certificate chain file used for the SSL connection during SMTP server authentication
- Does not result in any certificate checking, just gets passed to the underlying SSL connection
- Optional, defaults to None
EMAIL_SSL_KEYFILE
- Path to a PEM-formatted private key file used for the SSL connection during SMTP server authentication
- Does not result in any certificate checking, just gets passed to the underlying SSL connection
- Optional, defaults to None
DEFAULT_FROM_EMAIL
- Email address to use for various automated correspondence
- Optional, defaults to 'webmaster@localhost' in Debug mode
- Optional, defaults to EMAIL_USER setting value in Production mode
GOOGLE_OAUTH2_KEY
- Social authentication key for Google authentication
- Optional, defaults to None
- If not specified, Google login will be disabled
GOOGLE_OAUTH2_SECRET
- Social authentication secret for Google authentication
- Optional, defaults to None
- If not specified, Google login will be disabled
REDIRECT_HTTPS
- Force headers to HTTPS (used when behind a reverse proxy)
- Optional, defaults to 'False'
HIDE_API_DOCS
- Disables API endpoint documentation
- Optional, defaults to 'False'
GOOGLE_WHITELISTED_DOMAINS
- Google domains allowed to authenticate using Google login
- Optional, defaults to []
GOOGLE_WHITELISTED_EMAILS
- Google email addresses allowed to authenticate using Google login
- Optional, defaults to []

Registration Options

Account registrations can be enabled by changing the "GUEST_REGISTRATION" config to either "INVITE" or "PUBLIC".

"INVITE" registration requires that a registration token be sent to the prospective guest. Tokens can be generated within the 'Admin Console'.

"PUBLIC" registration is completely open. Anyone who signs up can create an account.

Additional Commands / Utilities

Yara rule files can be ingested automatically using the following command line Utilities.

UploadDirectory: This command will recursively traverse specified directories and process all yara rule files present. If the folder_as option is used, the field specified will be replaced with the folder name that the file is located in. Please note that the folder name will be 'forced' and therefore added to the groups options even if it did not previously exist.
```
pipenv shell
python manage.py UploadDirectory {DIRECTORIES} --source={SOURCE} --category={CATEGORY} --user={USER} --group={GROUP} --folder_as={source|category}
```

UploadMasterFile: This command will process a master file and its associated imports

pipenv shell
python manage.py UploadMasterFile {MASTERFILES} --source={SOURCE} --category={CATEGORY} --user={USER} --group={GROUP}

Rule Access

Each user has their own rule context/corpus which they completely control
- Each rule context/corpus operates individually from all others
- Users can share/collaborate on different contexts
- Members are only able to View and Submit Rules.
- Owner/admins of a context are able to View, Add, Edit, and Delete Rules.
- Owner/admins of a context can be manage Sources and Categories
- Owner is the only one who can manage members/admins
Additional contexts can be generated

REST API Driven

Uses Django REST Framework so you can automate or build a new UI for rule management. Endpoint documentation can be found at /API on a running instance of YaraGuardian.

Contributing

For those who are interested in contributing to YaraGuardian, please take a moment to look over the contribution guidelines.

ozanunal0/YaraGuardian