Home
Managing application risk
Follow this workflow to manage application security risks in your organization.
Step 5: Measuring progress and demonstrating compliance
Learn how to measure progress and demonstrate compliance.
Demonstrating compliance
Learn how to demonstrate compliance.
Industry standard reports
Learn about Industry standard report.
SANS/CWE Top 25 Most Dangerous Programming Errors v1.03 report
This report displays SANS/CWE Top 25 Most Dangerous Programming Errors issues found on your site. It matches issue types by CWE values. Many web application vulnerabilities might lead to security breaches of personal information, directly or indirectly, and might be considered as violations of the regulation.

Managing application risk
Follow this workflow to manage application security risks in your organization.
- Step 1: Creating an application inventory
  Learn how to create an application inventory.
- Step 2: Testing applications for vulnerabilities
  Learn how to test vulnerabilities identified in an application.
- Step 3: Determining risks and prioritizing vulnerabilities
  Learn how to determine risks and prioritize vulnerabilities identified in an application.
- Step 4: Remediating risks
  Learn how to remediate risks identified in an application.
- Step 5: Measuring progress and demonstrating compliance
  Learn how to measure progress and demonstrate compliance.
  - Measuring progress
    Learn how to track various metrics and trends of the applications that compose your portfolio.
  - Demonstrating compliance
    Learn how to demonstrate compliance.
    - Exporting issues as reports
      You can generate customized reports (in PDF, HTML, or XML) for issues and send them to developers, internal auditors, penetration testers, managers, and the CISO. The reporting templates in AppScan Enterprise map application security data to key government regulations and industry standards. Use the reports to document progress towards regulatory compliance goals, such as showing a reduction in the number of application vulnerabilities that are associated with compliance issues.
    - Limiting the size of a Security report
      Security reports can be large. During report generation, you might receive a warning message that the file is hundreds of pages long, or the report creation process might time out. Try the following tips to reduce report size.
    - Compliance Report
      Learn about Compliance report.
    - Industry standard reports
      Learn about Industry standard report.
      - International Standard ISO 27001 report
        This report displays existing web application vulnerabilities that violate this standard control objectives. The control objectives as listed in this standard are directly derived from and aligned with the control objectives listed in ISO 17799.
      - International Standard ISO 27002 report
        This report displays existing web application vulnerabilities that violate this standard control objectives. The control objectives as listed in this standard are directly derived from and aligned with the control objectives listed in ISO 17799.
      - NERC Cyber Security Standards report
        This report displays NERC Cyber Security Standards issues found on your site. Many web application vulnerabilities might lead to security breaches of personal information, directly or indirectly, and might be considered as violations of the regulation.
      - NIST Special Publication 800-53 Revision 4 report
        This report displays NIST issues found on your site. Many web application vulnerabilities might lead to security breaches of personal information, directly or indirectly, and might be considered as violations of the regulation.
      - OWASP Top 10 2013 report
        This report displays OWASP Top 10 2013 issues found on your site.
      - SANS/CWE Top 25 Most Dangerous Programming Errors v1.03 report
        This report displays SANS/CWE Top 25 Most Dangerous Programming Errors issues found on your site. It matches issue types by CWE values. Many web application vulnerabilities might lead to security breaches of personal information, directly or indirectly, and might be considered as violations of the regulation.
      - WASC Threat Classification v2.0 report
        This report displays WASC threat classification issues found on your site.

SANS/CWE Top 25 Most Dangerous Programming Errors v1.03 report

This report displays SANS/CWE Top 25 Most Dangerous Programming Errors issues found on your site. It matches issue types by CWE values. Many web application vulnerabilities might lead to security breaches of personal information, directly or indirectly, and might be considered as violations of the regulation.

Why it matters

The CWE/SANS Top 25 Most Dangerous Programming Errors v1.03 is a list of the most significant programming errors that can lead to serious software vulnerabilities. They occur frequently, are often easy to find, and easy to exploit. They are dangerous because they will frequently allow attackers to completely take over the software, steal data, or prevent the software from working at all.

This is a brief listing of the Top 25 items, using the general ranking.

Rank	ID	Name
1	CWE-89	Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
2	CWE-78	Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
3	CWE-120	Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
4	CWE-79	Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
5	CWE-306	Missing Authentication for Critical Function
6	CWE-862	Missing Authorization
7	CWE-798	Use of Hard-coded Credentials
8	CWE-311	Missing Encryption of Sensitive Data
9	CWE-434	Unrestricted Upload of File with Dangerous Type
10	CWE-807	Reliance on Untrusted Inputs in a Security Decision
11	CWE-250	Execution with Unnecessary Privileges
12	CWE-352	Cross-Site Request Forgery (CSRF)
13	CWE-22	Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
14	CWE-494	Download of Code Without Integrity Check
15	CWE-863	Incorrect Authorization
16	CWE-829	Inclusion of Functionality from Untrusted Control Sphere
17	CWE-732	Incorrect Permission Assignment for Critical Resource
18	CWE-676	Use of Potentially Dangerous Function
19	CWE-327	Use of a Broken or Risky Cryptographic Algorithm
20	CWE-131	Incorrect Calculation of Buffer Size
21	CWE-307	Improper Restriction of Excessive Authentication Attempts
22	CWE-601	URL Redirection to Untrusted Site ('Open Redirect')
23	CWE-134	Uncontrolled Format String
24	CWE-190	Integer Overflow or Wraparound
25	CWE-759	Use of a One-Way Hash without a Salt