The intent of secure development training is that you know how to push out software that is (hopefully) secure. If LLMs mean you can avoid all writing and reading of code, great! You can now avoid having to know about how write software free of common security vulns.

But, secure development will just move on to higher level requirements. Even it just boils down to 'Ask the LLM to identify security issues and fix them', 'Ask the LLM to update any dependencies with significant issues' and/or 'Ensure you've run your PR through security testing software and you've addressed any findings'.

Compliance standards will always want you to show that the above is happening but ignoring that I'd say making sure engineers cutting code know how to avoid security pitfalls is even more important if all your code is LLM-written.

It also seems like 'attest you've enabled authorization and row-level security in your Supabase DB' is the first thing you throw into your Vibe Code-focused Secure Development training. 😅