GeneXus Community Wiki
MENU
PAGE INFO
PAGE TOOLS
Add a category
Add a group
CREATE NEW PAGE
TBWelcome
Login
Register
Settings
Change Password
Logout
Search
Recents
i
Text Block
Managing OWASP Top 10 2017 in GeneXus Applications
Page Id
39915
A1: 2017 - Injection
A2:2017 - Broken Authentication
A3:2017 - Sensitive Data Exposure
A4:2017 - XML External Entities (XXE)
A5:2017 - Broken Access Control
A6:2017 - Security Misconfiguration
A7:2017 - Cross-Site Scripting (XSS)
A8:2017 - Insecure Deserialization
A9:2017 - Using Components with Known Vulnerabilities
A10:2017 - Insufficient Logging and Monitoring
Security Scanner built-in tool
GeneXus Security Scanner extension
GeneXus Security Scanner extension - Advanced Configurations
OWASP Top 10 2017 Security Scanner extension - Reference Table
A9:2017 - Using Components with Known Vulnerabilities
This documentation is valid for:
OWASP Documentation
Actions by GeneXus
GeneXus uses a set of public standard classes. You can find them
here
.
GeneXus updates its dependencies on every release.
GeneXus fixes known vulnerabilities on its releases.
Actions by Developers
Upgrade to the latest GeneXus's version.
Verify third party component used against Known Vulnerabilities Data Bases, mailing lists, etc.
Check for User controls,
Extensions
,
Patterns
and
External Objects
dependencies.
Security Scanner helps to detect this scenario with case codes #120 & #121.
Change the Data Base driver to the latest on deploy.
Verify the server's software is up to date.
Implement security policies.
Page Id
39934
Anchor
Next →
NextNode
Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Sure!
No
Additional feedback?
comment
Thank you for your feedback!
Backlinks
See all
Forward links
See all
More from lsilveira
See all
Contributions by
EDIT
—
CREATED: 9 JULY 2018 03:21 PM -
UPDATED: 20 JUNE 2023
08:03 PM
BY
LSILVEIRA