Page 19 - Security/OWASP

A single accidental commit containing database credentials or the crypt key from app/etc/env.php can compromise an entire Magento project, even after the repository is later set back to private. This article explains which files must never end up in Git, what a clean gitignore baseline looks like, and how a secrets manager and pre commit scanning reliably prevent it.

The Permissions-Policy header lets a page decide which powerful browser interfaces such as camera, microphone or location can be used at all, both for the page itself and for any embedded iframes. We cover the syntax, the difference from its predecessor Feature-Policy, and a practical configuration for a typical Magento shop.

A Docker image is made up of many layers of code someone else wrote: the base distribution, system-wide packages, a language runtime, and application dependencies. Any of those layers can carry known vulnerabilities without a developer ever having written a single line of that code themselves. Automated image scanning in the CI/CD pipeline surfaces those vulnerabilities before an image is even built toward production, preventing known gaps from quietly going live.

Role-based access control with ROLE_ADMIN and ROLE_USER rarely suffices in practice. When a user may only edit their own resources, only team members should have access, or permissions depend on the state of the object, the Symfony Security Voter is the right answer.

Credentials end up far too often directly in the repository, in plaintext configuration files or as a hard coded constant right in the middle of the code. Solid secrets management separates configuration from code, encrypts values at rest and turns rotation into a routine task instead of an emergency after a security incident.

Passing a password as a command line argument leaves it permanently in Bash history, visible to anyone who later uses the same shell. This article shows how secrets end up in Bash history, the process list, and logs, how HISTCONTROL and safe handoff methods prevent that, and how to search existing history files for forgotten credentials.

A threat modeling workshop without a fixed structure quickly loses momentum, because participants either stay too abstract or get lost in the details of individual components without systematically covering all relevant threat categories. The STRIDE methodology provides exactly this structure by offering six clearly delineated threat categories that get worked through per system component, turning an open discussion into a repeatable, complete process.

Security Misconfiguration is, according to OWASP, one of the most common vulnerability classes in production web applications, arising from default settings that were never hardened. This article shows how default credentials, verbose error messages, unnecessary modules, missing security headers, and a forgotten Magento Developer Mode hand attackers an open door, and how to systematically close every one of these traps.

Self-signed certificates constantly trigger browser warnings and can't be used for APIs or service workers. Combining mkcert with a Docker reverse proxy solves the problem completely: local domains with real, trusted HTTPS, no cloud, no Let's Encrypt, no endless clicking.

Every time a page loads a script from an outside CDN, it silently trusts that the code delivered today is the exact code that got tested. If that CDN is compromised, the file's contents can change while the referenced URL stays identical, and the browser happily loads the tampered code anyway. Subresource Integrity addresses exactly this gap: a hash value embedded in the HTML compares the content actually received against the content expected, and blocks execution the moment they diverge.