You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`Nothing about content security policy on there. I think that’s a big one. Most important place to have your CSP locked down is on the checkout page.
Recommendation - use a read only filesystem. Use Docker and checksum your images.
Firewall your entire site and make sure it’s not doing any outbound connections (unless you know what those are).
Secure your backups! You don’t need access to the database if you take your backups and put them in a public S3 bucket.
Your backups should have the same security as root access to your database. They should also be encrypted so they can’t just be transferred around.
Be careful with any PII. Don’t be lazy and make a copy of your production database for devs to put on insecure machines (their laptops) that they take on the train, airports, etc. Make a development database. Use mocks. Use test data.
That brings me to the next point - your whole system is completely insecure if the person with all of the keys is running on an insecure computer. Mandate that anyone with production access has an up-to-date anti-virus program, they are trained in how to detect phishing attacks, they have secure passwords/keys, their browsers are up-to-date and all of the plugins on that are up-to-date.`
The text was updated successfully, but these errors were encountered:
Talk to your vendors. Make them tell you what the URLs are that they’ll be sending requests to. Ask them to give you a npm package instead of hosting assets on their site.
It may sound dismissive and probably arrogant, but if a vendor can’t do that for me, why should I use their service? If a customer’s data is breached on my site, due to a vendor, I’ll be the one getting sued.
@joshuaadickerson I have added all your notes except the ones regarding outbound connections and vendors pending clarifications. Here are my questions:
Do you have any more details on recommended patterns for determining out bound connections on Magento sites?
Can you explain a little more by what you mean by your comment re: vendors and npm packages? I am unclear what you're recommending here.
`Nothing about content security policy on there. I think that’s a big one. Most important place to have your CSP locked down is on the checkout page.
Recommendation - use a read only filesystem. Use Docker and checksum your images.
Firewall your entire site and make sure it’s not doing any outbound connections (unless you know what those are).
Secure your backups! You don’t need access to the database if you take your backups and put them in a public S3 bucket.
Your backups should have the same security as root access to your database. They should also be encrypted so they can’t just be transferred around.
Be careful with any PII. Don’t be lazy and make a copy of your production database for devs to put on insecure machines (their laptops) that they take on the train, airports, etc. Make a development database. Use mocks. Use test data.
That brings me to the next point - your whole system is completely insecure if the person with all of the keys is running on an insecure computer. Mandate that anyone with production access has an up-to-date anti-virus program, they are trained in how to detect phishing attacks, they have secure passwords/keys, their browsers are up-to-date and all of the plugins on that are up-to-date.`
The text was updated successfully, but these errors were encountered: