rwhitman/salesforce tls1.0

## salesforce tls1.0
Email sent from Salesforce June 15 2015

## Product & Service Notification

As an admin for a Salesforce org that may use TLS 1.0 encryption to connect with external channels, we want to inform you of a change regarding supported encryption protocols. Over the next 12 months, Salesforce is preparing to disable TLS 1.0 encryption in a phased approach to prevent it from being used to access the Salesforce service during inbound and outbound connections.

Why is this happening?
At Salesforce, trust is our #1 value, and we take the protection of our customers' data very seriously. To maintain the highest security standards, and promote the safety of your data, we occasionally need to make security improvements and retire older encryption protocols. To maintain alignment with these best practices and updated compliance requirements from the PCI Security Standards Council, Salesforce will be disabling the use of TLS 1.0 for inbound and outbound connections to Salesforce.

What does this mean for me?
After Salesforce disables TLS 1.0 encryption, any channels connecting to Salesforce will need to use TLS 1.1 encryption or higher. Channels attempting to connect to Salesforce using encryption protocols lower than TLS 1.1 will NOT be able to connect to Salesforce. This includes browsers and any integrations to Salesforce APIs using unsupported encryption protocols.

What action do I need to take?
In order to maintain seamless access to your Salesforce orgs, you need to ensure browsers and integrations connecting to Salesforce have TLS 1.1 encryption or higher enabled. If your browser or integration does not have TLS 1.1 or higher enabled after we make this change, then your users will NOT be able to access Salesforce. We recommend you begin planning to support the TLS 1.1 encryption protocol or higher as soon as possible.

When will Salesforce begin disabling TLS 1.0?
Starting in the first quarter of calendar year 2016, Salesforce will begin disabling the use of TLS 1.0 for inbound and outbound connections using a phased approach.

Salesforce will disable TLS 1.0 over a series of maintenance windows that will be extended for this activity. We will announce the exact date and time of each maintenance window approximately two months prior to the window.

Where can I get more information?
Reminder notifications will be sent with additional information within 3 months time. In the meantime, we recommend you begin planning to support TLS 1.1 encryption protocol or higher as soon as possible.

For any additional questions, please reach out to Customer Support by opening a case via the Help & Training portal.
	Email sent from Salesforce June 15 2015

	## Product & Service Notification

	As an admin for a Salesforce org that may use TLS 1.0 encryption to connect with external channels, we want to inform you of a change regarding supported encryption protocols. Over the next 12 months, Salesforce is preparing to disable TLS 1.0 encryption in a phased approach to prevent it from being used to access the Salesforce service during inbound and outbound connections.

	Why is this happening?
	At Salesforce, trust is our #1 value, and we take the protection of our customers' data very seriously. To maintain the highest security standards, and promote the safety of your data, we occasionally need to make security improvements and retire older encryption protocols. To maintain alignment with these best practices and updated compliance requirements from the PCI Security Standards Council, Salesforce will be disabling the use of TLS 1.0 for inbound and outbound connections to Salesforce.

	What does this mean for me?
	After Salesforce disables TLS 1.0 encryption, any channels connecting to Salesforce will need to use TLS 1.1 encryption or higher. Channels attempting to connect to Salesforce using encryption protocols lower than TLS 1.1 will NOT be able to connect to Salesforce. This includes browsers and any integrations to Salesforce APIs using unsupported encryption protocols.

	What action do I need to take?
	In order to maintain seamless access to your Salesforce orgs, you need to ensure browsers and integrations connecting to Salesforce have TLS 1.1 encryption or higher enabled. If your browser or integration does not have TLS 1.1 or higher enabled after we make this change, then your users will NOT be able to access Salesforce. We recommend you begin planning to support the TLS 1.1 encryption protocol or higher as soon as possible.

	When will Salesforce begin disabling TLS 1.0?
	Starting in the first quarter of calendar year 2016, Salesforce will begin disabling the use of TLS 1.0 for inbound and outbound connections using a phased approach.

	Salesforce will disable TLS 1.0 over a series of maintenance windows that will be extended for this activity. We will announce the exact date and time of each maintenance window approximately two months prior to the window.

	Where can I get more information?
	Reminder notifications will be sent with additional information within 3 months time. In the meantime, we recommend you begin planning to support TLS 1.1 encryption protocol or higher as soon as possible.

	For any additional questions, please reach out to Customer Support by opening a case via the Help & Training portal.