Killbox, LLC (@_killbox) header
Killbox, LLC (@_killbox) profile picture

Your SOC, without the build. Killbox delivers WitFoo-powered SIEM, reporting, investigation, and response from one hosted platform.

Grand Rapids, MI
Joined August 2018
Photo by Killbox, LLC (@_killbox)Photo by Killbox, LLC (@_killbox)Photo by Killbox, LLC (@_killbox)Photo by Killbox, LLC (@_killbox)Photo by Killbox, LLC (@_killbox)Photo by Killbox, LLC (@_killbox)Photo by Killbox, LLC (@_killbox)Photo by Killbox, LLC (@_killbox)Photo by Killbox, LLC (@_killbox)
Replying to @johnhenrydev
Howdy Sir! I am also in Michigan (near GR). I might give pood.fit a try - I like to lift heavy things. My lovely wife might like GardenKeeper. I think my boys would get a kick out of StoneScout too! Best of luck with your apps ๐Ÿซก
1
14
Killbox, LLC retweeted
CFOs: ask every security vendor for a three-year price curve with your data volume doubled. Per-appliance pricing is predictable. Volume-, event- and token-scaled pricing surprises you at renewal. witfoo.com/research/ai-cost-โ€ฆ
1
1
7
Replying to @maaaxritz
we do that shit all the time ๐Ÿ˜Ž
12
site updated to show the simplest pricing you've ever seen. $50k per conductor and you get a full featured SIEM with: - UNLIMITED ingestion - NO rules/parsers to maintain - FULL integration support - AI Harness - Granular signal search - Comprehensive investigation capabilities - SOAR playbooks + AI enabled playbooks - Compliance tracking & reporting - a ton more join us: killbox.com
4
Replying to @Cyb3rMik3
Love this! Agreed on all points. Flat pricing, published for public consumption: witfoo.com/pricing How our model works (what's reduced before ingestion): vimeo.com/1246664434/75c5d1cโ€ฆ "Practitioners deserve real data" damn straight they do, and the only real way to determine "market-tecture" vs "solid capability" is a PoC/PoV. This is where SIEMs fall flat. Splunk, Sentinel, and others have significant engineering time and effort requirements. Ours don't. Set up a trial Conductor to forward logs and after an hour of setup/install you'll see the real features, against your real data.
12
Replying to @UK_Daniel_Card
nerd: "check out CVE-2026-123456, are we vulnerable?" ai: <spends a billion tokens> yes nerd: "no fun, can it be patched?" ai: <spends a billion tokens> yes nerd: "ugh, sounds like a lot of work. can you do it for me?" ai: <spends a billion tokens> yes nerd: "ok, go! uhh wait, I forgot ... MAKE NO MISTAKES!" ai: <spends remaining tokens> Your organization has reached its usage limit.
1
17
Replying to @Cyb3rMik3
I don't know what's more surprising: needing a "cost calculator" to ballpark what a SIEM will cost you, or celebrating its release as some huge improvement. There are a few great SIEM products out there, but MOST are priced in an insanely expensive and complex way. We don't have to live like this.
21
Your SIEM needs a "cost calculator" ๐Ÿ˜‚ .. and it includes variables outside of your control (ingestion volume) My SIEM keeps your costs flat. No calculators. Priced by appliance.. not ingest. join us: killbox.com
If you have ever attempted to perform capacity planning for ๐— ๐—ถ๐—ฐ๐—ฟ๐—ผ๐˜€๐—ผ๐—ณ๐˜ ๐—ฆ๐—ฒ๐—ป๐˜๐—ถ๐—ป๐—ฒ๐—น maybe 4 or 5 years ago, I am sure you remember the struggle. Archiving was harder (and often more expensive), log ingestion required far more complex technical architecture, and estimating costs with confidence wasโ€ฆ letโ€™s just say, not straightforward. Fast forward to today, and things have changed sฬฒiฬฒgฬฒnฬฒiฬฒfฬฒiฬฒcฬฒaฬฒnฬฒtฬฒlฬฒyฬฒ. Microsoft has just introduced a new ๐— ๐—ถ๐—ฐ๐—ฟ๐—ผ๐˜€๐—ผ๐—ณ๐˜ ๐—ฆ๐—ฒ๐—ป๐˜๐—ถ๐—ป๐—ฒ๐—น ๐—–๐—ผ๐˜€๐˜ ๐—–๐—ฎ๐—น๐—ฐ๐˜‚๐—น๐—ฎ๐˜๐—ผ๐—ฟ, and it is a major step forward in simplifying how we approach planning and cost estimation for SIEM deployments. With this new experience, estimating Sentinel costs becomes: ๐— ๐—ผ๐—ฟ๐—ฒ ๐˜๐—ฟ๐—ฎ๐—ป๐˜€๐—ฝ๐—ฎ๐—ฟ๐—ฒ๐—ป๐˜ โ€“ clearer visibility into ingestion, retention, and archive scenarios ๐— ๐—ผ๐—ฟ๐—ฒ ๐—ฝ๐—ฟ๐—ฒ๐—ฑ๐—ถ๐—ฐ๐˜๐—ฎ๐—ฏ๐—น๐—ฒ โ€“ better alignment between expected and actual costs ๐— ๐—ผ๐—ฟ๐—ฒ ๐—ฎ๐—ฐ๐—ฐ๐—ฒ๐˜€๐˜€๐—ถ๐—ฏ๐—น๐—ฒ โ€“ no need to build complex spreadsheets or reverse-engineer pricing models This is important for potential customers who consider moving to Sentinel, as well as for existing customers who need to continuously review and optimize their environment. What is even more significant is the impact on ๐——๐—ข๐—ฅ๐—”-๐—ฟ๐—ฒ๐—ด๐˜‚๐—น๐—ฎ๐˜๐—ฒ๐—ฑ ๐—ถ๐—ป๐˜€๐˜๐—ถ๐˜๐˜‚๐˜๐—ถ๐—ผ๐—ป๐˜€. The ability to model and reassess capacity in a structured and repeatable way provides strong support for ๐—”๐—ฟ๐˜๐—ถ๐—ฐ๐—น๐—ฒ ๐Ÿณ (๐—œ๐—–๐—ง ๐˜€๐˜†๐˜€๐˜๐—ฒ๐—บ๐˜€, ๐—ฝ๐—ฟ๐—ผ๐˜๐—ผ๐—ฐ๐—ผ๐—น๐˜€ ๐—ฎ๐—ป๐—ฑ ๐˜๐—ผ๐—ผ๐—น๐˜€), specifically the requirement to ๐—ฟ๐—ฒ๐—ด๐˜‚๐—น๐—ฎ๐—ฟ๐—น๐˜† ๐—ฎ๐˜€๐˜€๐—ฒ๐˜€๐˜€ ๐—ถ๐—ป๐—ณ๐—ฟ๐—ฎ๐˜€๐˜๐—ฟ๐˜‚๐—ฐ๐˜๐˜‚๐—ฟ๐—ฒ ๐—ฐ๐—ฎ๐—ฝ๐—ฎ๐—ฐ๐—ถ๐˜๐˜† ๐—ฎ๐—ป๐—ฑ ๐—ฝ๐—น๐—ฎ๐—ป ๐—ณ๐—ผ๐—ฟ ๐—ด๐—ฟ๐—ผ๐˜„๐˜๐—ต. In other words, this is not just a pricing tool, it is becoming an enabler for both better architecture decisions and stronger regulatory alignment. Check the tool here: microsoft.com/en-us/securityโ€ฆ
1
441
ghosted. Because his answer would have been "none". Conductor (our log collector/preprocessor) enables you to make such routing decisions. Based on classification. After enrichment. Granularly. Efficiently. join us: killbox.com
1
We've kicked Cribl's ass in every head-to-head we've done. Their reduction of logs kept is NOT deterministic! Their methods use sampling, which will certainly throw some needles out with the haystack. ... and yes, the cost of Cribl eats most of the Splunk "savings". We produce 90%+ ingestion reduction (WITHOUT sampling), and provide the SIEM all-in-one product. join us: killbox.com
Ive heard Cribl eats the costs that you save from Splunk, but that could be FUD. Are there quantitative examples of where Cribl reduces spend to a net total lower for Splunk AND Cribl?
34
My man gets it - why would your SIEM charge you for ingest/bandwidth? Greed. There's a better way. join us: killbox.com
I'll rather go with a platform that has BIG DATA platforms at its backend (Kafka, Cassandra, Node.J, Elastic search,etc) that way has the capacity to ingest just ANY amount of logs and flows (even if you have 100 of them). Pricing is never based on EPS nor Bandwidth consumed.
8
The big dawgs have figured out how to get you to subscribe annually to the data it requires to do its job. Imagine spending $$$$$ on Splunk and then needing to spend $$$ on Cribl just to reduce your storage costs and not go broke. Imagine spending $$$$ + $$$ and then still needing to pick and choose which logs to send into the system, so you don't go broke. Now imagine a SIEM that doesn't make you maintain every detection rule/parser, doesn't ever charge you on ingest volume, and gives you a predictable and sustainable cost while encouraging you to send all of the logs you have. join us: killbox.com
Replying to @FrankMcG
Splunk or Sentinel CAN be really cost effective. Especially leveraging tools like @cribl_io and having really serious conversations about your collection management framework.
10
This post is from 2023. After a great deal of thought and deliberation, Splunk and Sentinel have decided to become even more expensive. join us: killbox.com
Splunk and Sentinel costs. ๐Ÿคฏ How do you actually justify ROI? Thereโ€™s no way. I knew they were decently expensive, but like I thought maybe 30% of where it is. This market needs a hella correction. Have gotten way too greedy.
6
Replying to @Niyazhn45
Would you protect your endpoints with only detections based on virus definition files? Nope. SIEM has evolved as well, rules cannot solve this by themselves. Join us: killbox.com
1
Replying to @Niyazhn45
hit me up when you decide Splunk can't continue eating your soul
2
You shouldn't have to fight your SIEM. 90% noise you say? Now you have to turn whatever nerd knobs Splunk has to silence that 90% without losing the 10% - Splunk can engineer this but they don't, because they're a megacorp that doesn't care about its users. Join us: killbox.com
Honest question for SOC analysts: Our Splunk instance fires ~4k alerts/day, rule 101 (failed TLS handshake on 443) is 90% noise. How do you set a realistic false-positive target for such a rule?
2
Replying to @Niyazhn45
You shouldn't have to fight your SIEM. 90% noise you say? Now you have to turn whatever nerd knobs Splunk has to silence that 90% without losing the 10% - Splunk can engineer this but they don't, because they're a megacorp that doesn't care about its users. Join us: killbox.com
1
mannn I messed up. I started liking things on my business profile that I would typically like on my personal account and now they're indistinguishable ๐Ÿ˜ญ Someone quick complain about your SIEM so I can like, QT, and bookmark that shit like a thousand times.
1
๐ŸšจBREAKING๐Ÿšจ All of these tech outages seem to originate in Wuhan Province. The servers reside in the "Wuhan Institute of Offensive AI". Seems like it's just a coincidence though, more likely that two RATs combined code to form some type of malevolent AI entity.
2
Watch the replay of WitFoo Analytics 1.2.0 launch webinar. Great info about how WitFoo can leverage AI without making you poor ๐Ÿค‘ app.livestorm.co/witfoo/witfโ€ฆ
2