Closed
Bug 1155981
Opened 11 years ago
Closed 10 years ago
[mig agent] sandbox javascript interpreter to perform pre/post processing of operations
Categories
(Enterprise Information Security Graveyard :: MIG, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jvehent, Assigned: jvehent)
References
Details
When an agent executes N operations, each operation is ran in parallel against its own instantiation of a module. Results are aggregated into a JSON array and sent back to the scheduler. Modules don't know about each other and have no way to interact.
The ability to chain the work of modules would open new forensics options. The proposed workflow is to chain operations like unix commands are chained with pipes: the output of a module could become the input of another module.
To achieve this, we need a data transformation layer that convert the output of operation 1 into an input for operation 2. That layer could be performed by a lightweight javascript interpreter. Instead of running in parallel, operations would run in sequence, following the ordering of the operations array, with javascript transformation performed in between each operation.
The javascript interpreter must run into a sandbox. It must not be allowed to perform IOs. The agent must control the stdin and stdout of a javascript sandbox.
Group: mozilla-employee-confidential
Component: Operations Security (OpSec): MIG → MIG
Product: mozilla.org → Enterprise Information Security
Version: other → unspecified
| Assignee | ||
Updated•11 years ago
|
Group: mozilla-employee-confidential
| Assignee | ||
Comment 1•10 years ago
|
||
Migrated to github issues: https://github.com/mozilla/mig/issues
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: Enterprise Information Security → Enterprise Information Security Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•