Difference between revisions of "OWASP Top10:2021"
From Documentation
(Created page with "[https://owasp.org/Top10/ OWASP Top10:2021]") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | = OWASP Top 10 Security Concerns 2021 = | |
| + | |||
| + | == A04:2021 - Insecure Design == | ||
| + | ZK 10.0.0 addresses insecure design through several security enhancements, reinforcing the framework's defense against potential threats: | ||
| + | * '''Stricter GET/POST Handling''': To prevent HTTP verb tampering attacks, ZK 10.0.0 has refined how GET and POST requests are processed. It now returns a 404 error if an Asynchronous Update (AU) request is incorrectly sent via GET, ensuring proper usage of HTTP methods. | ||
| + | * '''Enhanced Security Framework''': ZK 10.0.0 integrates three advanced security checks into our CI/CD process: | ||
| + | * '''Synk Scanning''': This tool analyzes both source code and third-party dependencies for vulnerabilities. | ||
| + | * '''CodeQL PR Scanning''': It assesses pull requests for Java, JavaScript, and TypeScript to find security flaws before they are merged. | ||
| + | * '''SonarCube''': It scans the source code comprehensively to identify bugs, vulnerabilities, and security risks. | ||
| + | * '''Enable InaccessibleWidgetBlockService by Default''': In ZK 10.0.0, the InaccessibleWidgetBlockService, which blocks requests from inaccessible widgets, is enabled by default. This feature enhances security by preventing interactions with UI components that should not be accessible, such as disabled or hidden components. | ||
| + | |||
| + | == A08:2021 - Software and Data Integrity Failures == | ||
| + | While the ZK Framework itself does not manage software and data integrity directly, it is recommended that applications leveraging ZK implement appropriate controls. This includes the use of secure build pipelines, artifact verification, and runtime protection mechanisms to ensure data integrity throughout the application lifecycle. | ||
| + | |||
| + | == A10:2021 - Server-Side Request Forgery (SSRF) == | ||
| + | ZK Framework provides mechanisms for making server-side requests, but protection against SSRF largely rests with the application developers. It is essential to employ strict input validation, use allowlisting for accessible internal systems, and restrict unnecessary HTTP endpoint exposures. Ensuring that URLs or resources requested by server-side components are validated and secure is crucial. | ||
Revision as of 10:42, 13 May 2024
OWASP Top 10 Security Concerns 2021
A04:2021 - Insecure Design
ZK 10.0.0 addresses insecure design through several security enhancements, reinforcing the framework's defense against potential threats:
- Stricter GET/POST Handling: To prevent HTTP verb tampering attacks, ZK 10.0.0 has refined how GET and POST requests are processed. It now returns a 404 error if an Asynchronous Update (AU) request is incorrectly sent via GET, ensuring proper usage of HTTP methods.
- Enhanced Security Framework: ZK 10.0.0 integrates three advanced security checks into our CI/CD process:
* Synk Scanning: This tool analyzes both source code and third-party dependencies for vulnerabilities. * CodeQL PR Scanning: It assesses pull requests for Java, JavaScript, and TypeScript to find security flaws before they are merged. * SonarCube: It scans the source code comprehensively to identify bugs, vulnerabilities, and security risks.
- Enable InaccessibleWidgetBlockService by Default: In ZK 10.0.0, the InaccessibleWidgetBlockService, which blocks requests from inaccessible widgets, is enabled by default. This feature enhances security by preventing interactions with UI components that should not be accessible, such as disabled or hidden components.
A08:2021 - Software and Data Integrity Failures
While the ZK Framework itself does not manage software and data integrity directly, it is recommended that applications leveraging ZK implement appropriate controls. This includes the use of secure build pipelines, artifact verification, and runtime protection mechanisms to ensure data integrity throughout the application lifecycle.
A10:2021 - Server-Side Request Forgery (SSRF)
ZK Framework provides mechanisms for making server-side requests, but protection against SSRF largely rests with the application developers. It is essential to employ strict input validation, use allowlisting for accessible internal systems, and restrict unnecessary HTTP endpoint exposures. Ensuring that URLs or resources requested by server-side components are validated and secure is crucial.