CAPES has been updated to @elastic 7.8, @portainerio
1.24.0, @giteaio 1.13.0, @rocketchat
3.3.3, @EtherpadOrg 1.6.5, @TheHive_Project 3.4.0-1, Cortex 3.0.1-1, @drawio
13.2.5, and @GCHQ #CyberChef 8.22.0 capesstack.io
New release of CAPES! Most updated containers of @rocketchat, @giteaio, @TheHive_Project (incl. Cortex), @drawio, Mumble, and CyberChef. Huge update to the @elastic Stack with version 7.7.0, which includes case management! capesstack.io
Replying to @TheHive_Project
@TheHive_Project and Cortex are now the latest web apps behind the single SSL reverse proxy. Look at 'em there, pretty maids all in a row.
What's that? You want @packetbeat and #auditbeat monitoring CAPES? I got you. Check it out at buff.ly/2IDKbgn
We've updated to @elastic 7.4, which includes (among other things) Snapshot management from within Kibana and many new ML jobs for the SIEM app. Check it out at buff.ly/2F0aFWH
I'm happy to announce that the landing page for CAPES is now behind TLS (finally). I apologize for the delay, but it took me a long time to get the CSS to work through HTTPS in the Nginx container. Up next, update to a full TLS reverse proxy. buff.ly/2F0aFWH
Testing is completed and CAPES is running with @Elastic 7.3! The new Uptime and Infrastructure apps look great. Check it out over at buff.ly/2F0aFWH buff.ly/2yG92dv
Happy 4th of July in the US! CAPES is updated to @elastic 7.2.0. Next up, Auditbeat for the host. Check it out over at buff.ly/2F0aFWH
We're happy to announce that CAPES has been updated to @Elastic 7.1.1 buff.ly/2F0aFWH
We've finally added @drawio to CAPES. Check it out for campaign and adversary infrastructure diagramming! buff.ly/2IDKbgn
Replying to @elastic
@elastic has moved its security features down into the Basic License (which is the default distribution of the Stack and free). We're following this closely and will be rolling out an update to CAPES that will include TLS and RBAC! Stay tuned! buff.ly/2VR3D12
Using @elastic's Uptime and @portainerio's app, we were able to identify a functional issue with a service in CAPES. The issue was identified, remediated, and reported to the project owners! buff.ly/2IDKbgn buff.ly/2VWCoBD
















