There's some places where they show that twitter's public statements, after a security incident, around their security posture were misleading. That's potentially illegal, but even that could be a grey area.
There's some places where they show twitter didn't comply with creating and enforcing an SLDC, but if you've ever worked on an SLDC, you know it's a joke that's there for compliance checkbox reasons. Also, this is certainly a grey area because most likely to actually comply with this, you only need to have a document generated, training for how it should be used, and very basic processes in your git workflows. I'd be surprised if they hadn't done enough to legally comply with this.
The statements around "employees with production access" are vague. What _kind_ of production access do they have? If you're an engineer, you have production access, because your code can be deployed there. If you're in ops/support, you have production access, because you need to access user data. Hard to properly judge the seriousness of this without knowing more details.
For me, the lack of audit access seems to be the biggest legal issue, especially if they were lying to regulators about their progress.
It's not that the accusations aren't bad. They paint a picture of an org that has serious security issues, seriously management and organizational health/culture issues, flailing executives, and an incompetent board. But, it really seems like most of it simply isn't illegal.