This is the reason why AI companies offer controlled-access programs, which are actually not that hard to quality for.
There's no universal solution to this, other than vetting (the author in fact, doesn't provide any policy alternative) - if AI companies loosen the safeguards, people will complain for the opposite reasons.
They offer a great alternative that puts policy in the hands of users, where it belongs:
> Predictably, the only way to actually make our own service more secure ended up involving the use of EU-hosted open weights models, such as GLM 5.3, that actually complied with our intentions, proved that the issue is there, and then helped fix and verify that the issue is now resolved, for good.
The author doesn't offer a policy alternative because they make the argument that any proposed policy will slow down good actors while not slowing down bad actors, hence all possible policies make the world less safe when compared to a no policy world.
Not sure I would agree with that. But if you made me argue against it, I'd probably lose the debate.
That said, I took the author's invitation to read the requirements and, indeed, they are ornate. Especially if you want to red team your own product. https://support.claude.com/en/articles/14604842-cyber-verifi...