There is an old Dutch saying which goes: "Trust comes afoot and leaves on horseback". When you're in the compliance business you cannot fumble this ball, but you have.
> we built on an Apache 2.0 open-source repository, which explicitly permits commercial use, and significantly rebuilt it for compliance use cases
This framing is misleading. Apache 2.0 permits commercial use, but it also requires you to retain copyright/attribution notices, include the license, and add prominent notices to modified files.
Also hard to square “the allegations are fabricated” with simultaneously offering free re-audits, halting audit automation, and rebuilding the entire auditor network.
The problem with Apache 2 is it might not be completely clear how this works with a Saas product. Of course if you are distributing binaries or source to customers then you are going to run into issues with Apache Licensing. But if you are just running code on your servers then its not so straight forward. However, I guess its likely they were distributing javascript code so that could be a problem for them. Also, I guess regardless of the licensing issues not being honest with your customers when you are a compliance company is not going to be great for business.
I don’t understand the screenshot, the “attacker” sent that to customers? Or Delve created this screenshot as a dramatic reenactment? The post is not clear
their entire defense is "we are totally trustworthy! it's not our fault some 'bad client' opened and shared a spreadsheet we negligently used as a publicly accessible database of our fraud"
There are numerous contradictions in their messaging. They admit the data matches, but is being misconstrued, but they're going to rebuild their network and reaudit customers anyway. I can only assume they've received advice on this poorly thought out message delivery from the same place they received that awkward gesture and body language coaching. I'm sorry to say that the combination comes across as insincere.
It's important to note that pathological liars don't stop lying. In fact, when they're caught lying red-handed, they usually double down and lie even more.
There is an old Dutch saying which goes: "Trust comes afoot and leaves on horseback". When you're in the compliance business you cannot fumble this ball, but you have.
I don't see a way to recover frankly
Their existing customers are seriously exposed, i don't see this going anywhere except court
The problem is the malicious intent, you just can't do that anywhere, esp not in a trust based business..
The CEO is a clear scammer. How anyone trusts another word out of her math is beyond belief.
> we built on an Apache 2.0 open-source repository, which explicitly permits commercial use, and significantly rebuilt it for compliance use cases
This framing is misleading. Apache 2.0 permits commercial use, but it also requires you to retain copyright/attribution notices, include the license, and add prominent notices to modified files.
Also hard to square “the allegations are fabricated” with simultaneously offering free re-audits, halting audit automation, and rebuilding the entire auditor network.
Also: you'd expect a compliance company to understand basic software licensing, especially the most popular.
The problem with Apache 2 is it might not be completely clear how this works with a Saas product. Of course if you are distributing binaries or source to customers then you are going to run into issues with Apache Licensing. But if you are just running code on your servers then its not so straight forward. However, I guess its likely they were distributing javascript code so that could be a problem for them. Also, I guess regardless of the licensing issues not being honest with your customers when you are a compliance company is not going to be great for business.
I don’t understand the screenshot, the “attacker” sent that to customers? Or Delve created this screenshot as a dramatic reenactment? The post is not clear
their entire defense is "we are totally trustworthy! it's not our fault some 'bad client' opened and shared a spreadsheet we negligently used as a publicly accessible database of our fraud"
I love the spin:
Not "finding new auditors to replace those that want nothing to do with us and our standards were shite"There are numerous contradictions in their messaging. They admit the data matches, but is being misconstrued, but they're going to rebuild their network and reaudit customers anyway. I can only assume they've received advice on this poorly thought out message delivery from the same place they received that awkward gesture and body language coaching. I'm sorry to say that the combination comes across as insincere.
The founder is a Forbes 30u30 according to his X profile. As they say, you can't make these things up.
wasn't there some meme that 30u30 was some kind of predictor for fraud
Subject being discussed here:
https://news.ycombinator.com/item?id=47634690
They look guilty in that picture
Why is this post flagged? Is Delve brigading it?
They sound like me when I was learning SOC2. Ooh now I think I sorta get it. Lucky for me I was a mere employee and had consultants helping me.
It's important to note that pathological liars don't stop lying. In fact, when they're caught lying red-handed, they usually double down and lie even more.
I also assume these damage control type missives to be very misleading. Seen so many of these on HN over the years.
At the bottom of the page, I see an ad claiming “don't let manual compliance slow you down.” That really seems tone deaf lol