51 Kenna Security incidents · luty 2023 — official updates, affected components, duration and resolution details.
Problem został zidentyfikowany i jest w trakcie wdrażania.
Wprowadzono rozwiązanie i monitorujemy wyniki.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Obecnie badamy tę kwestię.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
Virtual Tunnel clients are unable to establish connection. Connector runs using Virtual Tunnel are returning failures. We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Users might be experiencing delays and timeouts when navigating the CVM dashboard and performing data updates. We are currently investigating this issue.
The issue has been identified and fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Multiple GCP services are currently experiencing partial outages or degraded performance. This is impacting key components of the CVM platform across several environments.
Google Cloud Platform has started mitigating the issue. CVM services are becoming more stable, but we’re still monitoring closely as GCP continues to stabilize.
CVM services have stabilized across all environments, and we're monitoring closely to ensure continued performance.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented., The MS Defender TVM connector is importing fewer assets than usual.
A fix has been implemented and we are monitoring the results.
The root cause has been identified and platform improvements have already been implemented. The Engineering team is currently monitoring the system, and connector runs have stabilized across the affected environments
This incident has been resolved.
We are currently investigating the issue
A fix has been implemented and we are monitoring the results.
We have released a potential fix for the outage you may have experienced and will continue to monitor the situation.
This incident has been resolved.
Connector runs might be stalled. We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are rolling back the recent NACL-related change to restore affected services
This incident has been resolved.
Qualys connector runs might fail with the error: "There was an issue parsing Qualys' response, which appears to be malformed XML. Please re-run your connector, and contact support if this issue persists." An internal error is returned by Qualys when retrieving the host list. We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with a 3rd party for failed responses [MS Defender TVM.] This issue is isolated to the single 3rd party. We are currently unable to extract data from their endpoint.
The MS Defender TVM Connector issue has been identified as isolated to a 3rd party service degradation. This is currently affecting our ability to retrieve vulnerability data, resulting in failed responses from the MS Defender TVM endpoint, we are actively weighing possible workarounds to mitigate the impact while awaiting further updates from Microsoft.
The CVM engineering team has identified an issue with the Microsoft Defender for Endpoint APIs. Currently, attempting to export files from the following endpoint: https://api.securitycenter.microsoft.com/api/machines/SoftwareVulnerabilitiesExport results in a 404 error indicating that the specified blob does not exist. As a temporary workaround, we have moved the vulnerability extracts to the SoftwareVulnerabilitiesByMachine endpoint. Please note this endpoint operates significantly slower than the file export previously used, therefore, we expect connector runs to take longer than usual while the workaround is in place. The engineering team will continue collaborating with Microsoft to revert to the original file export API once the issue is resolved.
This incident has been resolved.
The issues is identified and we are currently deploying a fix.
We are continuing to work on a fix for this issue.
All impacted environments have the fix and we are monitoring.
Systems have been functioning as normal for the last 3+ hours, moving this incident to resolved.
US Prod 1 is experiencing a backlog, customers may experience slow response times and 504 errors. We are currently investigating this issue.
We are continuing to investigate this issue.
Metrics in homepage and dashboard risk meter page have been temporarily disabled to alleviate the observed performance issues. We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
Connector runs for multiple connectors are not able to complete. We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing an issue with NVD data integration
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Connector runs are paused. We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently receiving reports of failures in connector runs with our third-party service, Qualys. We are actively monitoring the situation.
This incident has been resolved.