Security/OWASP: Guides and Practical Know-how | Page 15 | mironsoft Blog
Security/OWASP
-
Jul 15, 2025
Anyone who finds a security flaw in someone else's web application runs into a simple but unresolved problem: who do you actually tell? Without a clear point of contact, many reports end up in a generic support inbox, get ignored, or, out of frustration, get posted publicly on social media instead. RFC 9116 solves this with a refreshingly simple idea: a standardized text file at a fixed path that bundles contact details, deadlines, and signatures for responsible reporting.
-
Jul 13, 2025
API reviews without a systematic checklist consistently miss the same categories: security aspects, error formats, performance and test coverage tend to get skipped under time pressure. A structured checklist makes reviews faster, more complete and repeatable, and ensures that no PR gets merged with a critical gap.
-
Jul 12, 2025
Login forms without a well thought out brute-force defense are among the most exploited entry points in Magento stores. This article shows how rate limiting, progressive delay, account lockout, and risk-based CAPTCHA work together, without locking out legitimate customers or hurting conversion, including Magento's built-in protections and concrete configuration examples.
-
Jul 12, 2025
A cookie consent banner gets set up once in many projects, visually signed off, and then barely treated as its own, test-worthy functional area again, even though this exact area has a direct legal dimension: if a tracking script loads despite an actively declined consent, that's not a cosmetic detail, it's an actual violation of the General Data Protection Regulation with potential fine consequences. An automated E2E test that deliberately simulates different consent states and verifies whether tracking scripts actually load depending on that state makes this legally relevant functionality just as reliably regression-safe as any other critical business process in the store.
-
Jul 11, 2025
A convenient remember me feature and secure session handling are not mutually exclusive, once you know the right building blocks. This guide shows persistent remember me tokens instead of insecure signed cookies, protection against session fixation, and a timeout strategy that matches the actual sensitivity of the application.
-
Jul 10, 2025
Introspection is one of the most elegant properties of GraphQL, letting you query the entire schema through a request. That exact feature is what makes it risky in production: anyone who knows the API can read internal field names, mutations with access to sensitive data, and even deprecation comments, without guessing a single endpoint. Anyone who does not deliberately secure introspection hands attackers the full map of their own API.
-
Jul 9, 2025
PHP security is more than a single function or a framework feature, it encompasses input validation, output encoding, session hardening, secrets management, CSRF protection, security headers, clean error handling and dependency security as one coherent system. This article gives the complete overview of the security best practices that every production PHP application needs, regardless of the framework in use.
-
Jul 9, 2025
The Docker socket is often mounted as a convenient trick so a container can start other containers itself. What gets overlooked most: reaching that socket effectively grants root privileges on the entire host, no --privileged flag required.
-
Jul 8, 2025
Third party extensions inherit the same privileges as the Magento core and become the single biggest supply chain risk in a store. This article shows how to spot eval and base64 encoded payloads, check a vendor's reputation, apply static analysis with PHPStan, and test new extensions in an isolated sandbox before they go live.
-
Jul 3, 2025
The moment a team senses that working through a security incident will end with naming a guilty party, behavior during that process changes: details get withheld, timelines get smoothed over, and uncomfortable questions get avoided. A blameless postmortem consistently shifts the focus away from who made a mistake and toward what conditions made that mistake possible in the first place, and that shift demonstrably produces more honest, more complete reports.