NOTE: This put up covers an essential announcement associated to renewal of Symantec Server Intermediate Certificates Authority (ICA) and an upcoming swap of AWS IoT Core – management aircraft endpoints and newly supported AWS IoT Core buyer endpoints to TLS1.2 specification.

Overview

On this put up, we focus on upcoming modifications to Symantec Server Intermediate Certificates Authority (ICA) and switching on TLS 1.2 by default for management aircraft endpoints. We may also share suggestions on the right way to use customized area and configurable endpoint options of AWS IoT Core.  Moreover, you’ll find out about methods to make use of client-side customized certificates (self-signed certificates) for gadgets connecting to a single trusted endpoint, thus eradicating uncertainties related to public CAs.

Change #1: updating Symantec Server ICA

To allow clients to make the most of the newest security measures by default, we’ll swap AWS IoT Core – management aircraft endpoints and newly created buyer endpoints to TLS1.2 and we can have a brand new server certificates that’s primarily based on the VeriSign Class 3 Public Major Certification Authority – G5. Moreover, for backwards compatibility causes, we’re leaving all present buyer endpoints at their present TLS model and settings. We suggest clients migrate present buyer endpoints to TLS1.2 or TLS 1.3 at their very own comfort by way of AWS IoT Core configurable endpoint function.

Replace of Symantec Server ICA (Intermediate Certificates Authority)

Present Symantec Server ICA expires on thirty first October 2023 and a renewed Symantec Server ICA shall be used to difficulty all Symantec Server-side certificates.

Server certificates chain of belief (Symantec)

Determine 1.0

This modification is just for data-plane and applies solely to Symantec endpoints. Clients utilizing Amazon Belief Companies (ATS) endpoints gained’t be affected. AWS recommends that you simply don’t use certificates pinning as a result of it introduces an availability threat. Nonetheless, in case your use case requires certificates pinning, AWS recommends that you simply pin to an ATS signed Amazon Root CA 1 or Amazon Root CA 3 as a substitute of an intermediate CA or leaf certificates. Your gadgets can proceed to hook up with AWS IoT Core if you happen to had initially pinned to Symantec Root CA (VeriSign Class 3 Public Major Certification Authority – G5).

Actions / suggestions:

• Present Symantec Server Intermediate Certificates Authority (ICA) certificates expires on thirty first Oct and we’re slowly rolling out a brand new server ICA certificates that’s primarily based on the VeriSign Class 3 Public Major Certification Authority – G5. AWS is rigorously monitoring the method and as we detect incompatible gadgets, we’ll attain out to our clients. Must you discover modified system conduct or incapability of your system to speak with AWS IoT Core, please contact buyer help or your Technical Account Supervisor (TAM).
• We strongly recommend eradicating any hard-coded affiliation to those distrusted Symantec Server ICA certificates and use publicly trusted Root CA (comparable to ATS signed Amazon Root CA 1  or Amazon Root CA 3), to make sure your functions stay safe and suitable.
• Use Amazon Belief Companies (ATS) endpoints and replace firmware to confirm full certificates chains in opposition to the ATS Root from right here. Put at the very least Amazon Root CA 1 and Amazon Root CA 3 within the system. Put all 5 within the retailer for max future compatibility when you have system capability.
• You probably have pinned to the Symantec Server Intermediate Certificates Authority (ICA) certificates and expertise a connection failure after an replace, please replace your firmware to confirm full certificates chains in opposition to the Symantec Root CA (VeriSign Class 3 Public Major Certification Authority – G5). Yow will discover this certificates right here.
• Use customized area and configurable endpoints.
  • Configurable endpoints mean you can management the TLS coverage utilized to your gadgets, and once more, this may be accomplished incrementally by creating an endpoint with new coverage, and transferring gadgets to it when they’re prepared.
• It is strongly recommended to have two separate endpoints: one for cellular apps utilizing Public CA, and one other particularly for gadgets utilizing a non-public CA (or self-signed) certificates, and be absolutely conscious of your TLS safety insurance policies.
• Don’t restrict certificates measurement on the client-side. Public CAs require server certificates to be renewed repeatedly. The addition of OCSP responder URLs and different choices can enhance the dimensions of a server certificates over time. We suggest including enough buffer to deal with future server certificates. You possibly can confirm your system’s compatibility with massive server certificates by way of AWS IoT Core Gadget Advisor.

Utilizing Amazon Belief Companies (ATS) signed Root CA

Listed here are steps to replace your gadgets to make use of an ATS signed Root CA:

1. Establish the Root CA that your gadgets are at present utilizing. You are able to do this by wanting on the server certificates chain introduced when your gadgets connect with AWS IoT Core.
2. Obtain the ATS signed Root CA from the AWS IoT documentation.
3. Set up the ATS signed Root CA within the belief retailer on your gadgets. The particular steps for doing this can differ relying on the kind of system you’re utilizing.
4. Check your gadgets to ensure that they’ll connect with AWS IoT Core utilizing the ATS signed Root CA.

Change #2: updating the TLS configuration

As a part of our continued dedication to safety, we’re happy to announce that AWS IoT Core – management aircraft endpoints and newly created buyer endpoints will now default to TLS 1.2 or above specs. This improve ensures that you simply profit from the newest safety requirements and enhancements within the business. We additionally wish to deliver to consideration that AWS shall be updating the TLS configuration for all AWS service API endpoints to a minimal of model TLS 1.2.

Actions / suggestions

• Management aircraft endpoints: If you’re utilizing TLS 1.0/1.1 then you have to to start out utilizing TLS 1.2 or increased for these connections.
• Knowledge aircraft endpoints:  Units connecting to AWS IoT Core utilizing TLS 1.0 / 1.1 will proceed to function as regular, however we advise updating these gadgets to help minimal model of TLS 1.2 for safety future-proofing functions.

Migrating your endpoints

To facilitate a seamless migration, we now have launched configurable endpoints that allow you to transition your present buyer endpoints to TLS 1.2 or TLS 1.3 at your comfort. This flexibility means that you can tailor the migration course of in response to your particular necessities and schedule. You possibly can comply with detailed directions in our earlier weblog put up.

Setup customized domains and configurable endpoints

To setup customized domains and configurable endpoints in AWS IoT Core to have better management over your server certificates and handle the behaviors of your information endpoints. You possibly can comply with detailed directions in our earlier weblog put up. Keep in mind to all the time take a look at your configurations completely earlier than deploying them in manufacturing environments.

Conclusion

On this weblog put up, we mentioned two essential bulletins that can assist future-proof your IoT deployments.

We bid farewell to Symantec Server ICA certificates, acknowledging their previous service, whereas additionally recognizing the necessity for stronger safety measures with our advice to make use of ATS signed certificates and ATS endpoints. By migrating to trendy SSL/TLS server certificates from trusted Certificates Authorities (CAs) comparable to ATS, you’ll be able to fortify your functions in opposition to superior cyber threats and guarantee compatibility with the newest browsers and gadgets.

Secondly, we embraced the newest TLS 1.2 requirements as default, transitioning away from TLS 1.0/1.1 and defaulting to TLS 1.2 onwards for AWS IoT Core’s management aircraft and newly created buyer endpoints.

Lastly, we advise to make the most of customized domains and configurable endpoints, providing you with better management over your server certificates and managing the behaviors of your information endpoints.

Continuously Requested Questions

Q1: How do I do know if I’m affected?

A: If you’re utilizing ATS Server certificates there aren’t any modifications. For Symantec Server certificates, confirm that your system’s TLS implementation doesn’t pin the ICA, wherein case you’re good. We will’t give generic directions on how to do that, however one factor we might doubtlessly recommend is to take a look at all of the certificates baked into your system code, and see if there’s one which expires in 2023. Or you possibly can affirm the baked in certs are Amazon Root CA 1 and Amazon Root CA 3 for ATS and Symantec VeriSign Class 3 Public Major Certification Authority – G5.

Q2: What if I discover a change in system communication conduct with AWS IoT Core?

A: Must you discover modified system conduct or incapability of your system to speak with AWS IoT Core, please contact buyer help or your Technical Account Supervisor (TAM).

The place can I get assist?

You probably have questions, contact AWS Assist or your technical account supervisor (TAM), or begin a brand new thread on the AWS re:Publish AWS IoT Discussion board.

Study Extra

To be taught extra about the advantages of TLS 1.2 and TLS 1.3 help in AWS IoT Core and the right way to make the transition, we invite you to go to our documentation:

• AWS IoT Core – management aircraft endpoints: Hyperlink
• AWS IoT Core – information aircraft endpoints: Hyperlink
• Configurable endpoint function: Hyperlink
• TLS 1.2 for all AWS API endpoints: Hyperlink
• AWS IoT Core transport safety: Hyperlink
• Issuing and managing certificates: Hyperlink
• Getting ready for AWS Certificates Authority: Hyperlink
• Migrating system fleets to AWS IoT Customized Domains:  Hyperlink
• AWS IoT ECC Assist: Hyperlink
• How AWS IoT Core is Serving to Clients Navigate the Upcoming Mistrust of Symantec Certificates Authorities: Hyperlink
• DigiCert Root certificates: Exterior Hyperlink

Concerning the Creator

Syed Rehan is a Sr. IoT Cybersecurity Specialist at Amazon Net Companies (AWS), primarily based in London and dealing throughout the AWS IoT Core Safety Foundations workforce. He serves a world buyer base, collaborating with safety specialists, builders, and safety decision-makers to advertise the adoption of AWS IoT companies. Possessing in-depth data of cybersecurity, IoT, and cloud applied sciences, Syed assists clients starting from startups to massive enterprises, enabling them to assemble safe IoT options throughout the AWS ecosystem.