-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for PoshC2 #22
Comments
At first glance, logging by PoshC2 seems somewhat similar to that of Cobalt Strike. So this should not be a lot of work. Generically speaking I expect the following things to be required to be created:
My main problem at this moment is that I have no experience with PoshC2 and don't have access to demo logs that I can test with. Any help with above steps is well received. Help with access to demo logs would also work. |
Here's some example files from a test VM.
rewrite-rules.txt |
Thanks, this is something we can work with. A few quick questions:
|
Ah great, thanks for clearing up the terminal/tmux setup! I believe I understand enough to get going. Few remaining things:
|
Every file relating to a project is kept in a project folder, which is usually in /opt/PoshC2_$PROJECTNAME (although configurable by the operator) The $PROJECTNAME is configured in the config.yaml in the /opt/PoshC2 folder. So you config up Posh, run posh-server, and it creates your /opt/Project_$PROJECTNAME folder, generates your Apache rewrite rules, preps the SQLiteDB, compiles all your payloads etc. |
Hey :)
in 'text' form.
|
Are these colouring characters really present in the raw log file, or is this an interpretation by Jimmy's terminal. Jikes, server time... Any way to make that UTC? Clear on the project names. I can have Filebeat understand this and work with those subdirs, no prob. |
They are present in the log file aye, which are then interpreted by the terminal as colours. For the time we can switch to UTC but I'm not sure if that's desirable; the operator may prefer timestamps in their local time making it easier to digest. That's one for @benpturner. |
Happy to help out with this btw if we get some direction. If you want to hop on a hangouts call or similar just DM me on twitter to set one up :) |
Thanks for the offer! The roadmap to have this included is listed above (#22 (comment)). Looking at my agenda for the next 1-2 weeks I don't see enough time to have a proper go at this. So feel free to start working on it. I think steps 1 (filebeat setup) and 2 (logstash filters) are easiest for you to pick up. The other items require specific RedELK knowledge. Overall, it certainly does help if you have previous experience with ELK (not RedELK per se). If not, there is a lot of info within RedELK already to leverage. For example: the filebeat config will largely be a modification of: https://github.com/outflanknl/RedELK/blob/master/teamservers/filebeat/filebeat.yml. For the logstash filter rule I expect https://github.com/outflanknl/RedELK/blob/master/elkserver/logstash/conf.d/50-c2-cobaltstrike.conf to be of great inspiration. If this feels to stretched for you, no worries. I'll pick it up when I see the time. Would be happy to discuss on a call when there is tangible progress. |
Added initial PR for this - #25 |
For the record (I previously commented on the PR not on the issue, my bad): I've included the pull request into the maindev branch that will become version2 in the coming time. I did some tuning to integrate it all into one directory (now only 1 dir for c2servers instead of separate dirs for every c2 framework) and modified the install scripts. I have tested it to the level I can without access PoSHC. Let me know your findings. Next steps are:
|
Awesome, will give this a test on the maindev branch. I’ll also try to sort the downloads for the screenshots, should be fairly straightforward I think. |
Gents, gentle request to test with latest RedELK version 2 BETA 1 release. There was significant overhauling of field names. We believe we got them all. But it couldn't hurt you PoshC2 expert do the final checking. |
Yeah 100% - looking forward to have a blast |
Having a few issues with install on the latest version, looking at the log its not overly helpful "status" : 400 |
Yes I agree that the logging is not that helpful. I just changed this a bit in commit 4a71fc7 (not part of a new beta release yet) That having said, it seems that your installation only had issues with importing Kibana prepared data. If this is the case, you will miss some easy-to-use things but its not a big issue per se. So perhaps your install might actually work. You may also be happy to know that we are working on a docker-compose version of the RedELK server, helping you with that install. Not ready yet, and prolly will take another few weeks. |
fyi, the v2.0.0-beta.3 release is out. This release has the elkserver side entirely overhauled into a docker-compose setup. Should make your life easier (although its still is beta, ) |
Hi - just trying the docker stuff and getting this on the initial install |
Had to modify these VARS in the .env before this installed |
[] Running initial Let's Encrypt script |
@benpturner on which version did you encounter the error? Regarding this one, I'm guessing this is executable bit missing
|
I checked out master today - is that the latest branch? |
Better use the latest release, beta3 in this case. Also, in your case as you are developing, you may want to pass the dev parameter to the install-elkserver.sh script. This ao will make sure the logstash config files are live mounted to files on your host. |
Have full support for the PoshC2 framework (https://github.com/nettitude/PoshC2).
I will need help from others with understanding the exact way of logging performed by PoshC2.
The text was updated successfully, but these errors were encountered: