Course contentsShow
← Security
Lesson 2706 of 3,05251. Mobile SecurityFree lesson

App Transport Security (ATS)

Learn ATS requirements for secure network connections, TLS configuration, and exception handling.

What You'll Learn

You'll learn how iOS's App Transport Security (ATS) enforces secure network connections by default, what its TLS requirements are, and when you might need exceptions.

What Is App Transport Security?

App Transport Security (ATS) is Apple's security feature that forces iOS apps to use secure HTTPS connections instead of plain HTTP. Think of it as a strict bouncer at a club who won't let anyone in without proper credentials—ATS won't let your app make network requests unless they meet specific encryption standards.

Introduced in iOS 9, ATS is enabled by default, blocking insecure connections automatically. This protects users from man-in-the-middle attacks, eavesdropping, and protocol downgrade attacks.

Core ATS Requirements

ATS demands that all network connections meet these standards:

  • TLS 1.2 or later (TLS 1.3 recommended)
  • Forward secrecy cipher suites (like ECDHE)
  • Certificates signed by a trusted Certificate Authority
  • SHA-256 or better certificate signatures
  • 2048-bit RSA keys minimum (or 256-bit ECC)

Connections failing these requirements are blocked unless explicitly allowed.

When Exceptions Are Necessary

Sometimes you must connect to legacy servers or third-party APIs that don't meet ATS standards. You can add exceptions in your app's Info.plist:

  • Domain-specific exceptions: Allow certain domains to use lower security
  • Arbitrary loads: Disable ATS entirely (strongly discouraged and requires App Store justification)
  • Local networking: Allow connections to unqualified domains/IPs for development

Apple reviews exception requests during App Store submission and may reject apps with unjustified exceptions.

Best Practices

Always aim to meet ATS requirements rather than request exceptions. Work with API providers to upgrade their TLS configurations. Use exceptions only temporarily during migration periods.

Key Takeaway: ATS enforces TLS 1.2+, strong ciphers, and valid certificates by default, blocking insecure connections to protect users—exceptions should be rare, specific, and well-justified.