Skip to end of metadata
Go to start of metadata
- Vulnerability Management is the process to handle security incidents.
- The process includes to act in a timely manner.
- The process includes joint action of the SOS development team and support team.
- Vulnerability Reporting
- Vulnerability Verification
- Change Proposals
Vulnerability Management Process
- Reports about vulnerabilities are forwarded to SOS
- Detection of vulnerabilities includes both the SOS software product and any 3rd party libraries included with the software product.
- Sources of vulnerability detection in source code of SOS software products include
- automated scans performed by source code repositories,
- security audits performed by users and customers for example for pen-testing,
- security breaches reported by users and customers.
- SOS tracks vulnerabilities in 3rd party open source libraries by automated scans provided by source code repositories,
- Users are advised to use private e-mail to report vulnerabilities.
- After receipt of a vulnerability report SOS sets up a task force to reproduce and to identify a reported vulnerability.
- This includes to identify affected releases of the software product.
- This includes to evaluate risks for a given vulnerability.
- This step typically is completed within 24 hours after receipt of a respective report.
- If a vulnerability is confirmed then the task force will
- request a CVE ID from https://www.mitre.org/ and will provide the respective CVE report that is not publicly available,
- add a private Change Request to the Change Management System,
- report back to the vulnerability reporter about the assigned CVE ID. This step is completed immediately after receipt of a CVE ID and depends on mitre.org response times.
Vulnerability Risk Mitigation
- Depending on the security risks identified with the previous step for verification of a vulnerability the following applies:
- for high-risk and for medium-risk vulnerabilities an alert is provided to customers who subscribe to this type of notification with their product support option.
- for low-risk vulnerabilities no information is provided to customers.
- Based on the criticality a release date is determined:
- For high-risk and for medium-risk vulnerabilities an immediate maintenance release date is planned for branches of the software product that are under maintenance.
- For low-risk vulnerabilities the typical release cycle of approx. 3 months or earlier is applied.
- Fixes are implemented within the scope of the Release Policy - Change Management.
- Fixes are provided for any branches of the software product that are under maintenance.
- Fixes are not made publicly available with the GitHub Source Code Repositories before communication.
- Fixes include the procedure to approve that an exploit of the vulnerability is no longer applicable.
- For high-risk and for medium-risk vulnerabilities this steps typically is completed within five business days.
- With fixes being available the following applies:
- Maintenance releases are published for download with the SOS web site and with SourceForge.
- Users should be aware that 3rd party web sites that mirror downloads of SOS software products might or might not indicate availability of maintenance releases. SOS denies any liability for accurate and timely downloads of maintenance releases available from 3rd party web sites.
- CVE Reports
- With downloads being available SOS asks mitre.org to make the CVE report publicly available.
- Notifications are made available with the "News" section of the SOS web site.
- Notifications are provided by RSS Feeds.
- Notifications are provided via Twitter News
- Customers who subscribe to notifications within their support option receive a notification by e-mail.
- The Product Knowledge Base is added the information with the list of Vulnerabilities.
- Fixes provided for any branches under maintenance are communicated at the same point in time.