App Transport Security provides a platform framework for network security. Define explicit, service-specific policies instead of broad exceptions.
Evaluation approach
Inventory contacted domains and necessary exceptions. Test which rules each networking library actually enforces.
Application example
Restrict an exception needed for a legacy service through a migration plan rather than extending it to every domain.
Limits and considerations
ATS alone does not resolve server authorization defects or in-app interference.
Give every exception an owner
ATS exceptions are often added for compatibility with an older service. An exception may remain in the project after the service changes. Record its justification, owner and removal condition.
Inspect settings in the final distribution output, not only the development project. Test whether failures cause a fallback to weaker connections. Secure defaults do not make a misconfigured server trustworthy; peer verification remains necessary.
Checks and decisions
- Narrow exceptions
- Test TLS failures
- Inspect dependency connections
Observe actual connection behavior across all networking layers in use.
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.