This repository has been archived by the owner on Oct 20, 2023. It is now read-only.
Brute Ratel Parser Alpha & Custom Parser Foundation #143
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add validate and info commands for both brute ratel and cobaltstrike parsers Add new parsers env variable Update campaign log upload form and endpoints Rename cs-parser to cobalt-strike-parser
Create core parser packages
Add migration scripts and run on gt dataset
Fix client graphql shape for parserInfo
Update cypress tests to use new tabs
Update README with config changes
Add description of parsing message properties and types
GoldingAustin
force-pushed
the
feature/brute-ratel-parser
branch
from
568fa50
to
877acae
Compare
Fix issue with single server uploads Fix migrations Misc fixes to types
Use root README within landing page
sharplessHQ
approved these changes
Jul 12, 2023
Update JSON schemas with improved documentation Update parsers with slight changes to types
…l-parser # Conflicts: # applications/client/src/store/graphql/BeaconMetaModel.base.ts # applications/client/src/store/graphql/HostMetaModel.base.ts # applications/landing-page/dist-landing/index.html # applications/server/schema.graphql # packages/migrations/src/campaign-migrations/.snapshot-campaign.redeye.json # packages/migrations/src/db-configs.ts
Update communication type enums to match case of values Fix enum values in parser output Fix beacon name loading check and display
sharplessHQ
pushed a commit
to sharplessHQ/RedEye
that referenced
this pull request
Sep 20, 2023
Co-authored-by: Austin Golding <austin.golding@pnnl.gov> Co-authored-by: Courtney Carpenter <ccarpenter28@gmail.com> Co-authored-by: Sebastian Ang <dajian.ang@pnnl.gov>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR covers two major areas:
The Brute Ratel parser uses the autosave.profile and logs folder created by Brute Ratel to generate a campaign. The nomanclature Brute Ratel uses has been integrated into the Server (listener), Host (host), and Beacon (badger) naming scheme.
The new parser system will be detailed further in an upcoming PR, which will map the full API and provide a guide to creating a custom parser that integrates with RedEye.
In short, to create a RedEye parser you must: Create a binary that supports at least a
parse-campaignandinfosub-command that supports outputs and inputs to and from the RedEye server. Then a user puts it in theirparsersfolder and enables it in their config. Everything else is handled by the RedEye server.Changes
parsersfolderparsersfield to the configParserInfotype