-
-
Notifications
You must be signed in to change notification settings - Fork 62
Overview
This is the name of the webserver that was build with the Django-Framework
MTV = model - template - views . The main idea behind django.
Make a model for your data - build a template for how the data is being presented to the user - define views for requests
EMBArk is currently in a pre-release state.
More info for Contributors.
EMBA provides the main functionalities for the Firmware-analyzing process. It`s run in a container.
We use a lightweight redis docker image for caching
Embark uses and depends on a MySQL-Database which is also run in a docker-container. It can be exported/imported/backed-up using the provided scripts
As the WSGI application we use a standalone Apache-webserver Apache serves all static source files and handles all processes related to synchronous requests that are not explicitly piped into the "bounded-executor".
As the ASGI application we use daphne for our Async requests (e.g Web-sockets)
EMBArk - firmware security scanning at its best
Sponsor EMBA and EMBArk:
The EMBA environment is free and open source!
We put a lot of time and energy into these tools and related research to make this happen. It's now possible for you to contribute as a sponsor!
If you like EMBArk you have the chance to support future development by becoming a Sponsor
Thank You ❤️ Get a Sponsor
EMBArk - firmware security scanning at its best
- Home
- Feature overview
- Installation
- Usage
-
EMBArk-book
- Overview of embark
- Chapter 1: User Authentication & Authorization
- Chapter 2: Firmware Analysis Management
- Chapter 3: Real-time Progress Monitoring
- Chapter 4: Reporting & Visualization
- Chapter 5: EMBA Backend Integration
- Chapter 6: Worker Node Orchestration
- Chapter 7: Background Task Execution
- Chapter 8: Data Models (Persistence Layer)
- Chapter 9: Deployment & Environment Setup
- Development
- FAQ
- Sponsoring EMBArk
- AMOS project archive
- EMBA firmware scanning backend