Which component enables software communication but is also a common attack vector that requires strong authentication, input validation, and rate limiting?

• A. SDKs
• B. Proxies
• C. APIs
• D. Firewalls

Answer: (C)

APIs are the interface that lets software talk to other software. Because they expose endpoints that external clients and other services call, they become a common attack surface. Securing them relies on strong authentication to verify who can access the API, input validation to ensure data is safe and won’t cause injections or processing errors, and rate limiting to prevent abuse, brute-force attempts, and denial-of-service pressure. Together, API authentication, input validation, and rate limiting protect the communication layer while keeping the integration open and functional.

SDKs, while they help developers integrate with services, are development-time tools rather than the live communication surface that external parties invoke. Proxies can mediate and sometimes filter traffic, but the key requirement described—a communication interface that must be protected with authentication, input validation, and rate limiting—best fits APIs. Firewalls protect the network boundary and aren’t the primary component that enables and secures software-to-software interactions at the API level.