From cfd11e545b142ea88c9b3133018435a3dc7fa9d3 Mon Sep 17 00:00:00 2001 From: Andy Rothfusz Date: Mon, 24 Jan 2022 10:49:14 -0500 Subject: [PATCH] Update SECURITY.md Remove unintended double negative --- SECURITY.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index b204f9fcda..00a72a9e07 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -1,5 +1,5 @@ ### Security Policy for Device SDKs -Amazon has updated the AVS API to add a new consent screen during device registration for new users if the device has not been not certified by Amazon. Once the device has completed the testing process including obtaining a security assessment from Authorized Security Lab and receiving an Alexa Built-in badge, this consent screen will be removed and developers will be able to offer the full Alexa experience on their Alexa Built-in devices. To learn more about device testing and certification, please visit [here](https://developer.amazon.com/en-US/alexa/devices/alexa-built-in/development-resources#additional-resources). +Amazon has updated the AVS API to add a new consent screen during device registration for new users if the device has not been certified by Amazon. Once the device has completed the testing process including obtaining a security assessment from Authorized Security Lab and receiving an Alexa Built-in badge, this consent screen will be removed and developers will be able to offer the full Alexa experience on their Alexa Built-in devices. To learn more about device testing and certification, please visit [here](https://developer.amazon.com/en-US/alexa/devices/alexa-built-in/development-resources#additional-resources). ### Reporting a Vulnerability -If you discover a potential security issue in this project we ask that you notify Alexa Voice Services Security team by sending an email to . Please do **not** create a public GitHub issue. \ No newline at end of file +If you discover a potential security issue in this project we ask that you notify Alexa Voice Services Security team by sending an email to . Please do **not** create a public GitHub issue.