Platform Security features Winter'16

We can use the new Health Check tool to identify and fix security risks in your password, session, and network access settings, all at a glance.

• View and Address Security Risks Using Health Checks
  At a glance, we can now see and fix security risks in your Session Settings, Password Policies, and Network Access settings. A new health check dashboard shows how well your org measures against the Salesforce-recommended baseline. Health Check lets you understand and proactively remediate your org’s security risks and vulnerabilities from a single page.This feature is available in both Lightning Experience and Salesforce Classic.
• Default Certificate is 2048 Bits
  If we use client certificates or custom web address https certificates, we can now create a 2048-bit certificate or a 4096-bit certificate. The option to create a 1024-bit certificate has been removed.
• Upgrade Your Transport Layer Security (TLS) Version for HTTPS Connections
  Starting in Spring ’16, Salesforce is disabling the TLS 1.0 encryption protocol using a phased approach. We can test and upgrade to TLS 1.1 or TLS 1.2 early to give our org more time to verify end-to-end compatibility. This feature is available in both Lightning Experience and Salesforce Classic.
• Use an API Client Certificate for Improved Scurity
  We can now choose an org-specific API client certificate for workflow outbound messages, the AJAX proxy, some ApexPageReference methods, and delegated authentication HTTPS callouts. This change improves security and maintains productivity after a planned Microsoft Windows update on April 19, 2016 that retires the root certificate of the older proxy.salesforce.com certificate