Pipeline Scan Partial Service Disruption when using OWASP 17
Incident
Report for Veracode
Resolved
This incident is resolved. Please revert any work arounds you might have implemented during the outage. Please ensure you are using the latest Pipeline Scan client, version 21.5.0-0 going forward.
If you have any other questions or concerns, please contact Veracode Support at support@veracode.com
If you have any other questions or concerns, please contact Veracode Support at support@veracode.com
Update
We continue to work on implementing the fix relating to this incident. In the meantime, as a work around, Customers can update their policies to remove “OWASP 2017” and replace it with “Auto-Update OWASP” to avoid the pipeline scan issue.
The next update will be available by 14:30 EDT.
The next update will be available by 14:30 EDT.
Update
We are continuing to work on a fix for this issue.
Identified
Veracode Engineering has identified the issue and is working to implement a fix.
The next update will be available by 11:00 EDT.
The next update will be available by 11:00 EDT.
Investigating
Veracode Engineering is actively investigating errors that is impacting customers using pipeline scanner that are relying on a policy file when policies include "OWASP 2017"'.
If you have any further questions or concerns, please open a ticket with Veracode Support at support@veracode.com. Thank you for your patience as we actively work to resolve this issue.
The next update will be available by 10:00 EDT.
If you have any further questions or concerns, please open a ticket with Veracode Support at support@veracode.com. Thank you for your patience as we actively work to resolve this issue.
The next update will be available by 10:00 EDT.
This incident affected: Static Analysis (Pipeline Scanner).