Plugin & Extension Security for AI: Complete Guide | QuizBy Eyal Doron / December 6, 2025 / 1 minute of reading Plugin & Extension Security for AI: Complete Guide | Quiz 1 / 7 1. What security testing framework does the article recommend before approving plugins? 1. Static analysis – dynamic analysis – integration testing – permission testing 2. Antivirus scanning of plugin files 3. Only manual code review by developers 4. User acceptance testing in production Correct! Why: The article recommends static analysis for code vulnerabilities plus dynamic analysis for runtime behavior plus integration testing for secure channels plus permission testing for least privilege. Context: This comprehensive testing catches different types of security issues before plugins enter production. Remember: Static – Dynamic – Integration – Permission testing. 2 / 7 2. What guidance does the article give for Anthropic Claude MCP security? 1. Use only public MCP endpoints for convenience 2. Disable MCP entirely as it cannot be secured 3. Allow all MCP tools without restriction 4. Host MCP servers internally – authenticate via mTLS or API keys – monitor unusual tool sequences Correct! Why: The article recommends hosting MCP servers internally and authenticating calls via mTLS or API keys and monitoring for unusual tool sequences. Context: Local MCP servers have file system access to the host machine making careful implementation review essential. Remember: Internal hosting – strong auth – watch for anomalies. 3 / 7 3. What is OWASP LLM #7 and why does it exist? 1. An encryption protocol for plugin communications 2. A certification standard for secure plugin development 3. Insecure Plugin Design – exists because plugin security is systematically weak across the industry 4. A specific type of malware that targets AI systems Correct! Why: OWASP LLM #7 addresses Insecure Plugin Design – it exists because plugin security is systematically weak across the industry. Context: Plugins often receive excessive permissions and lack input validation because they are built quickly with security as secondary. Remember: Assume plugins are insecure until proven otherwise. 4 / 7 4. How can prompt injection lead to plugin abuse according to the article? 1. Hidden instructions in content cause the AI to misuse legitimate plugins for unintended actions 2. Prompt injection only affects the AI response text not plugin behavior 3. Prompt injection requires physical access to the plugin server 4. Plugins are immune to prompt injection attacks Correct! Why: An attacker includes hidden instructions in content the AI processes causing the AI to use plugins in unintended ways like deleting files or sending data to attacker URLs. Context: The plugin itself may be legitimate – the attack exploits the AI role as decision-maker. Remember: Injected prompts make good plugins do bad things. 5 / 7 5. What is typosquatting in the context of plugin security? 1. Typing commands incorrectly into the AI system 2. Creating plugins with names similar to popular ones hoping users install the wrong one 3. Encrypting plugin communications with weak algorithms 4. Using keyboard shortcuts to bypass security Correct! Why: Typosquatting creates plugins with names similar to popular legitimate plugins hoping users install the wrong one – for example gcal-assistant vs gcal-asst. Context: This is a supply chain attack targeting plugin marketplaces by exploiting user typing errors. Remember: Wrong name – wrong plugin – real attack. 6 / 7 6. What are the three main plugin threat vectors identified in the article? 1. Encryption – hashing – tokenization 2. Authentication – authorization – accounting 3. Network attacks – application attacks – physical attacks 4. Malicious plugins – compromised plugins – exploited plugins via prompt injection Correct! Why: The article identifies plugins that can be the attacker (malicious) or the victim (compromised) or the weapon (exploited via prompt injection). Context: Defense must address all three vectors because each requires different security controls. Remember: Malicious – Compromised – Exploited. 7 / 7 7. What makes AI plugin security fundamentally different from traditional integrations? 1. Traditional integrations cannot connect to external systems 2. AI plugins require more bandwidth than traditional integrations 3. Traditional integrations are always less secure than AI plugins 4. The AI makes decisions about which plugins to call rather than humans explicitly choosing actions Correct! Why: With AI plugins the AI chooses which actions to take rather than humans explicitly choosing – and the AI can be manipulated through prompt injection. Context: This decision flow creates unique risk because attackers can influence the AI interpretation to trigger unintended plugin actions. Remember: The AI decides – and the AI can be manipulated. Your score isThe average score is 0% Restart quiz Download PDF Please leave this field empty๐ The AI Security Manager's Newsletter Weekly insights on AI risk management, EU AI Act compliance, and practical security strategies. We donโt spam! Read our privacy policy for more info. Thank you! Please check your inbox to confirm your subscription.
