In recent years new security standards were introduced or updated like ISO 27001 and NIS2. While there is some overlap in terms of what these standards ask for the scope of who needs to be compliant is steadily growing. Even if those standards do not yet apply to you the growing focus on software security will likely catch up with you soon. Considering PHP still has the reputation of being insecure it might be useful to check what the current state of tools and libraries is.
This talk introduces some of the legislation around software security and then, based on the DevSecOps maturity model, looks into concrete measures in PHP to satisfy some of the controls from these standards. It is important to note. While this provides only a very narrow look at these standards from a developer's perspective, ignoring some of the additional work around governance and policies (focusing on the build and implementation-phase), it should give you an idea where you might want to improve your security posture or dissuade concerns around not being able to create secure software with PHP.
Note: The slides are rather image heavy. If you have any questions or comments feel free to reach out to me.