DrRobinson

See `command:`

This comment seems out of place to me. It brings up (claimed) political issues irrelevant to the topic at hand.

The account is recently created and this is the first and only comment/post they've made on this site.

I think some of the information here is misleading and a bit unfair.

> being too intrusive and affecting their workflow

Kolide is a reporting tool, it doesn't for example remove files or put them in quarantine. You also cannot execute commands remotely like in Crowdstrike. As you mentioned, it's based on osquery which makes it possible to query machine information using SQL. Usually, Kolide is configured to send a Slack message or email if there is a finding, which I guess can be seen as intrusive but IMO not very.

> reading and reporting all files

It does not read and report all files as far as I know, but I think it's possible to make SQL queries to read specific files. But all files or file names aren't stored in Kolide or anything like that. And that live query feature is audited (ens users can see all queries run against their machines) and can be disabled by administrators.

> web browsing history

This is not directly possible as far as I know, but maybe via a file read query but it's not something built-in out of the box/default. And again, custom queries are transparent to users and can be disabled.

> Kolide's whole spiel about "honest security"[1] reeks of PR mumbo jumbo whose only purpose is to distance themselves from other "bad" solutions in the same space

While it's definitely a PR thing, they might still believe in it and practice what they preach. To me it sounds like a good thing to differentiate oneself from bad actors.

Kolide gives users full transparency of what data is collected via their Privacy Center, and they allow end users to make decisions about what to do about findings (if anything) rather than enforcing them.

> It's built by Facebook alumni, after all, and relies on FB software (osquery).

For example React and Semgrep is also built by Facebook/Facebook alumni, but I don't really see the relevance other than some ad-hominem.

Full disclosure: No association with Kolide, just a happy user.

It's news _from_ 2023, not news about things that happened only in 2023. Things might have improved starting years ago but the research to show it wasn't finished until this year, so it's also about celebrating seeing progress and improvements.

Limiting the list to things improving only since 2022 seems unnecessarily restrictive and we'd miss a lot of positive and interesting news.

Great to see your commitment but I'm also curious why you, unlike some other companies, have chosen not to support with any full time employees? It seems your business is largely based on Terraform and saying pretty much "we'll contribute code" doesn't signal too much commitment.

I realize my comment might sound like an accusation but that's not my intention, I want to hear your reasoning about it!

Trakt.tv is a good alternative to IMDb btw

This comment seems overly harsh in my opinion. I don't think the author comes off as a self-involved twat and I generally found the website helpful.

> Neither me nor my coworkers give a damn about being kind.

I don't see this as a good thing to "brag" about, and I think trying to do something about work being stressful is a good thing.

This is a scam rather than a phishing attack. They've set up fake stores to steal money, not a phishing site to steal credentials.

This would require you or the person in the data center to know which customer is using which disk. And data isn't stored on just one disk, it's spread out over multiple disks and many customers have shards of data stored on the same disk. So even if this did happen, the would only get fragments of data.

> This is a different argument.

Part of it, maybe. But the point about it reducing risk by very little is true.

> Did you see other comments in this thread, for example someone bought a drive online and turned out it still had some backblaze data?

Backblaze data is encrypted, or so they claim. Backblaze is also not hosted on AWS. I've also yet to see any evidence of that claim, though I don't dismiss it.

Data is sharded/spread out over multiple disks, you don't have one disk per customer and have all their data there. You'd get fragments of data. If Backblaze was running their servers on specific disks that were not encrypted, not zeroed, and not destroyed, that'll have to stand for them. Backblaze is hosted in a shared data center/colocation, while AWS has their own data centers with their own personnel. Backblaze is a separate company from AWS.