So which points are not fulfilled at the moment? Laravel by itself doesn't have any problems with PCI compliance, it is how you implemented things that can be non-compliant.
Making a Laravel Installation PCI Compliant
We have a distributed Laravel network where we have two installations interacting with the same DB. One installation has voyager installed on it for admin purposes and one is based on Lumen for Rest API's.
We're looking to make the entire network PCI Compliant so the personal data we store is secure and all the stakeholders are well rested. We have two options, either we make the entire network PCI Compliant or we move the personal data to a separate DB and installation, make that PCI Compliant and pseudonymize access.
Not sure if anyone has ever made a Laravel installation PCI Complaint, if yes please share some insights on your experience.
Also, we're using AWS as the hosting service, so any measures we can take there will also be really helpful
Please or to participate in this conversation.