-
-
Notifications
You must be signed in to change notification settings - Fork 62
API
In this section we will explain the api and the corresponding features. For a more detailed or practical view please refere to https://e-m-b-a.github.io/embark/ for the Swagger UI documentation.
- Login
- Go to this page [http://localhost:8001/user/] or via the sidebar.
- Generate an api key
The entire process is also shown in pictures down below
- The uploader can be accessed via [http://localhost:8001/api/uploader]
- Inside the Headers define "Authorization = 'API key' and inside the body create a field named "file" and as input 'Your File'
- This upload if successful will return a UUID
The status of the analysis can be checked via this url [http://localhost:8001/status_report/'YourUUID'], you will still need to define "Authorization = 'API key'". This returns a link to the report if the report is finished or else a status of the progess as shown down below.
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