OWASP-related security rules
These 7 dbLinter rules reference OWASP Top 10 risk categories (2021, 2025 editions) and help identify security issues in Oracle APEX applications. Each rule links to the relevant category and explains the finding with examples and a recommended fix.
Use these checks to review application access controls and security settings.
Rules by OWASP category
All 7 OWASP-related rules
-
A-0700 Always enable Session State Protection at the application level.Blocker Security
-
A-0720 Always enable Page Access Protection.Blocker Security
-
A-1100 New Try to keep hidden page items protected.Blocker Security
-
A-1340 Avoid pages without an authorization scheme.Critical Security
-
A-1410 Never set session lifetime or idle time to 0 (unlimited).Critical Security
-
A-2300 New Never use the HTML (Unsafe) format on Display-Only items.Critical Security
-
A-3080 New Avoid making Interactive Grid columns read-only with CSS only.Blocker Security
7 total
Related rule collections
- Trivadis PL/SQL & SQL guideline rules - Rules that implement the Trivadis coding guidelines.
- Oracle APEX rules - Checks for APEX applications, pages, items and regions.
- PostgreSQL rules - Rules that also apply to PostgreSQL and PL/pgSQL.
- Security rules - All rules in the Security quality area.
- Reliability rules - Rules that prevent bugs and failures at run time.
- Maintainability rules - Rules for code that is easy to read and change.
- Rules by quality area - Security, reliability and maintainability.
- Rules by severity - From Blocker to Info.
- Rule profiles - Essential to Extreme: which rules are checked.
- Rules by tag - Topics such as SQL, performance and naming.
- All rules - Search and filter the complete rule set.