Identified - The issue has been identified and a fix is being implemented.
Feb 22, 12:51 PST
Identified - Evident is aware of an issue causing some suppressions to not work as intended. A suppression rule that includes both built in and custom signatures may become deactivated when a new alert matching the suppression configuration is generated. Evident is working on this issue and we expect to have a fix deployed during the 2/28 maintenance. In the meantime, a workaround is to create separate suppressions for built in signatures and for custom signatures.
Feb 20, 13:52 PST
Update - We are finalizing testing of the adjustments to AWS:RDS-009 and currently plan to deploy these changes and re-enable the signature next week.
Feb 14, 13:33 PST
Identified - AWS:RDS-009 is temporarily globally disabled pending adjustments to its methodology. The adjustment will ensure that alerts will only be generated if the AWS account has any classic RDS instances.
Nov 30, 13:29 PST
Update - We have a potential solution now in QA and will provide additional updates as we approach release.
Feb 14, 10:40 PST
Identified - Currently, if an Azure external account does not have real-time alerting configured, alerts will not end when related resources are deleted. The root cause has been identified and engineering is actively working to fix this. For an immediate workaround you can configure real-time alerting (http://docs.evident.io/#azure-logs).
Nov 17, 11:16 PST
Update - The aforementioned fix is scheduled for release on 2/21.
Feb 14, 10:40 PST
Identified - We have identified the root cause and are finalizing tests on a potential fix, which will be deployed with the next ESP Web release.
Feb 7, 11:13 PST
Investigating - We have identified an issue with editing integrations. Editing and saving an existing integration will result in a 404 error. One workaround is to delete then recreate the integration. Make sure the settings are correct during integration creation. We will update this incident as soon as we have further information.
Jan 26, 10:09 PST
Investigating - We have received a few reports of an intermittent issue where individual alerts' status and metadata have not updated to reflect the latest information. We are investigating these incidents and will provide updates here as further information becomes available. Please contact us at support@evident.io if you have any questions or concerns.
Feb 2, 12:25 PST
Investigating - We have identified an issue with alerts when two or more external accounts use the same Azure Client ID and App Registration. Doing so will cause all external accounts with the shared ID and Registration to receive alerts from the one of the subscriptions, but none from the others. We are actively working to identify the root cause and implement a fix. For an immediate workaround, please configure the external accounts with different Client IDs.
Dec 7, 11:21 PST

About This Site

Welcome to the status page for the Evident Security Platform for AWS. At Evident.io we are committed to providing transparency around our operations, resiliency, and security and are happy to answer questions on these topics. To submit a question please contact us via our support email address - support@evident.io. Thank you for visiting!

Evident Security Platform API   Operational
Evident Security Platform Web UI   ? Operational
Evident Scanning Engine   Degraded Performance
Evident Custom Signature Engine   Operational
Evident Integration Engine   Operational
Evident User Attribution Engine   Operational
Evident Security Platform API (GovCloud)   Operational
Evident Security Platform Web UI (GovCloud)   Operational
Evident Scanning Engine (GovCloud)   Degraded Performance
Evident Custom Signature Engine (GovCloud)   Operational
Evident Integration Engine (GovCloud)   Operational
Evident User Attribution Engine (GovCloud)   Operational
AWS ec2-us-east-1   Operational
AWS ec2-us-east-1   Operational
AWS ec2-us-west-1   Operational
AWS ec2-us-west-2   Operational
AWS rds-us-east-1   Operational
AWS rds-us-west-1   Operational
AWS rds-us-west-2   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
We will be undergoing scheduled maintenance during this time.
Posted on Feb 22, 12:54 PST
Past Incidents
Feb 21, 2018
Completed - Our QA team has completed testing and no issues were found. The weekly scheduled deploy has been finalized.
Feb 21, 19:03 PST
Verifying - The weekly scheduled maintenance has been completed. Our QA team is currently verifying this week's deploy.
Feb 21, 13:29 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 21, 11:00 PST
Scheduled - We will be deploying bug fixes and new signatures to our scanning engine this week. Full details may be found at https://goo.gl/4nbq97. If you have any questions, please contact our support team at support@evident.io.
Feb 20, 10:31 PST
Feb 19, 2018

No incidents reported.

Feb 18, 2018

No incidents reported.

Feb 17, 2018

No incidents reported.

Feb 16, 2018
Completed - Unfortunately, today's e-deploy failed production QA acceptance and has been rolled back. If you have any questions or concerns, please reach out to support@evident.io.
Feb 16, 16:43 PST
Verifying - Our e-deploy has been completed and our QA team is currently verifying the update.
Feb 16, 12:16 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 16, 11:01 PST
Scheduled - We will be performing an e-deploy today to address incident http://status.evident.io/incidents/x7vjdf28htpv, as well as several other UI enhancements and bugfixes. For full details please see https://goo.gl/CdZtJh. If you have any questions please contact our support team at support@evident.io
Feb 16, 10:27 PST
Feb 15, 2018
Resolved - Evident has patched all of our systems as vendor patches came available and will continue to do so as new variants of "Meltdown" and "Spectre" are discovered and mitigated. As managing speculative execution side-channel attacks has become "the new normal", we are closing this event, but rest assured that Evident's security team will stay hard at work protecting our infrastructure and in turn, yours. If you have any questions or concerns around "Meltdown", "Spectre", or any of the recent variants, please reach out to security@evident.io.
Feb 15, 17:56 PST
Monitoring - The recently disclosed security vulnerabilities dubbed “Meltdown” and “Spectre” (CVE-2017-5715, CVE-2017-5753, and CVE-2017-5754) have exposed a speculative execution vulnerability in specific Intel, AMD, and ARM processors. These processors are globally used in nearly every operating environment on the planet; both datacenter and cloud provisioned computational systems are vulnerable to these attacks.


The Evident.io SecOps team responded under our emergency response plan to the early disclosure of this issue and executed necessary remediary measures to protect all critical compute systems in Evident.io’s operating environment(s). While the vast majority of Evident.io’s compute systems have already been protected, there are a small number of secondary nodes that are scheduled to be patched immediately as the industry responds to these emerging threats. Our security team is on high alert to ensure the safety and security of our customers, their data, and their trust in our platform. We feel it is of the utmost criticality that security vendors around the globe make public statements about their response, and demonstrate that we are rallying around our customers and peers to mitigate the risks these emerging threats pose to our global internet community. Our team is proud to be in the ranks of cloud giants like Google, Amazon, and Microsoft in demonstrating our capability to respond and defend those customers who make us successful.
Jan 4, 15:35 PST
Feb 14, 2018
Resolved - Our QA team has completed verification of the deployed fix. If you continue to have any issues, please contact our support team at support@evident.io
Feb 14, 09:36 PST
Monitoring - We have deployed a hotfix for this incident and we are currently monitoring the issue.
Feb 13, 14:47 PST
Identified - We have identified an issue where, when you enable a disabled signature, another signature may become enabled instead. A fix has been tested and will be released soon.
Feb 9, 16:57 PST
Feb 13, 2018
Completed - Our QA team has completed testing and no issues were found. The weekly scheduled deploy has been finalized.
Feb 13, 14:47 PST
Verifying - Our e-deploy has been completed and our QA team is currently verifying the update.
Feb 13, 11:59 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 13, 11:00 PST
Scheduled - We will be performing an e-deploy today to address http://status.evident.io/incidents/tk92wj4lys9b and make some minor backend adjustments. If you have any questions, please contact our support team at support@evident.io.
Feb 13, 09:44 PST
Feb 12, 2018
Resolved - Availability has been restored. We are continuing to monitor. If you have any questions or concerns, please contact us at support@evident.io.
Feb 12, 18:41 PST
Identified - Evident.io is experiencing reduced availability. Our engineers are engaged and we will provide updates here as we progress.
Feb 12, 18:22 PST
Resolved - The alert delays on newly created accounts have been resolved. We are also looking to improve this aspect to prevent alert delays from occurring.
Feb 12, 15:47 PST
Investigating - We are investigating alert delays on newly created accounts. Our engineering team is aware of the issue and will provide updates as we investigate.
Feb 8, 09:47 PST
Feb 11, 2018

No incidents reported.

Feb 10, 2018

No incidents reported.

Feb 8, 2018
Completed - Weekly scheduled maintenance has been completed. No customer-facing changes were made.
Feb 8, 13:25 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 8, 11:00 PST
Scheduled - There are no customer-facing changes scheduled this week. If you have any questions or concerns, please contact our support team at support@evident.io
Feb 5, 10:53 PST