JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.

If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.

If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.

CodeSonar® 9.2p0 CONFIDENTIAL CodeSecure Inc

OWASP Top Ten Application Security Risks - 2017

The categories list for each CodeSonar warning includes any relevant members of the OWASP® Top Ten Application Security Risks - 2017.

A broader set of correspondences is shown in Broad Mapping: OWASP Top Ten Application Security Risks - 2017.

CSV tables of warning classes by OWASP-2017 rule are provided in OWASP-2017-mapping.csv.



The OWASP Top Ten 2017

"OWASP-2017" is shorthand for the OWASP Top Ten Web Application Security Risks - 2017.

See the OWASP Top Ten 2017 website for more information.

Relevant Warning Classes

The following table shows the CodeSonar warning classes that are associated with OWASP-2017 top ten security risks.

OWASP-2017 C/C++ Warning Classes Ada Warning Classes Java Warning Classes C# Warning Classes Kotlin Warning Classes Python Warning Classes
OWASP-2017:A1 Injection
OWASP-2017:A2 Broken authentication - -
OWASP-2017:A3 Sensitive data exposure - - - -
OWASP-2017:A4 XML external entities - -
OWASP-2017:A5 Broken access control
OWASP-2017:A6 Security misconfiguration -
OWASP-2017:A7 Cross site scripting (XSS) - - -
OWASP-2017:A8 Insecure deserialization - - -
OWASP-2017:A9 Using components with known vulnerabilities -
OWASP-2017:A10 Insufficient logging and monitoring - -

Management Reports

The predefined OWASP Top Ten 2017 Report management report template allows you to automatically generate a report summarizing all the warnings from a particular analysis that are closely mapped to one or more of the OWASP Top Ten Web Application Security Risks.

You can generate this report from the GUI Analysis page for the analysis of interest. For general instructions, see Task: Generate a Management Report.

Enabling OWASP-2017 Rules

Because the rules are strongly tied to web application development, many of the associated checks are disabled by default.

CodeSonar ships with a taxonomy preset for OWASP-2017 checks:

owasp2017 Enables warning classes such that a given class C is enabled if all of the following are true.
  • C is closely mapped to one or more OWASP-2017 members (that is, it appears in the table above), and
  • no other classes enabled by the preset are more closely related to the same rules, and
  • C is not diagnostic-only (that is, it does not have a DIAG.* mnemonic).

You can apply the owasp2017 preset to the CodeSonar build/analysis as shown in the following table.

@PRESET_TABLE[owasp2017]@

Enabling checks for specific security risks

To enable checks for all the warning classes associated with a specific OWASP-2017 security risk, include the following in the project configuration file:

WARNING_FILTER += allow categories:"OWASP-2017:Anum"

Enabling individual classes

To enable a single warning class check, follow the instructions in the documentation for the corresponding warning class. Warning class documentation links are provided above.


 

To report problems with this documentation, please visit https://support.codesecure.com/.