Vault7: CIA Hacking Tools Revealed
Navigation: » Directory » Philosoraptor » Philosoraptor Home » Meeting notes
Owner: User #524297
2014-12-01 Meeting notes
Date
Attendees
Goals
- To catalog and organize our plans for implementing Philosoraptor
Brainstorming
- Automated release builds for release candidates and evaluation copies
- Stoplight matrix for PSPPersonal Security Product (Anti-Virus) evaluation results
- Status wallboard for project including build status and sprint progress
- Manual step in release process to account for visual string analysis (automate this process?)
- Confluence space template for projects to create uniformity (Status/User Doc/Dev Doc)
CONOP
- One-line description: Simple dropper executed by double clicking.
- Witting user (asset) loads media into target computer that contains Philosoraptor executable
- Witting user copies Philosoraptor to target computer
- Witting user starts Philosoraptor executable to deploy payload to target
- Deploys to
%APPDATA% - Philosoraptor self-deletes after execution
- Deploys to
- Forensic record of media insertion (possible risk)
Working Agreement
- Git Workflows will be used for maintenance of development/release branches in Stash
- JIRA tasks will be tracked, one branch per JIRAUser Managment Software (Atlassian) task
- Meeting notes tracked in Confluence
- Automate execution of build process and testing, using Bamboo/DART where appropriate
- Keep commits small, work in feature branches, merge features by pull requests
- Pull requests adhere to recommendation list (future)
- Conduct team Retrospective after each Sprint
Action items
| ID | Status | Task |
|---|---|---|
| 1 | incomplete | Create Pull request TODO list for reference |