The correct answer is implementing strong authentication, authorization, and input validation. This approach ensures that only authorized users can access APIs (authentication), they can only perform allowed actions (authorization), and their inputs are properly validated to prevent injection attacks and other security issues. These controls address the most common API security vulnerabilities.
Making API documentation publicly available for comment may help developers use the API correctly but doesn't provide any security protection by itself. While documentation is valuable, it must be accompanied by actual security controls.
Limiting APIs to internal use only is an overly restrictive approach that prevents legitimate external integration, and internal APIs still need security controls since not all internal users should have unrestricted access to all APIs.
Encrypting all API traffic addresses data confidentiality during transit but fails to protect against unauthorized access or malicious inputs.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are the key components of strong authentication?
Open an interactive chat with Bash
How can you implement effective input validation for APIs?
Open an interactive chat with Bash
What are common API security vulnerabilities?
Open an interactive chat with Bash
ISC2 CISSP
Software Development Security
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access