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. User acceptance testing in production 2. Antivirus scanning of plugin files 3. Static analysis – dynamic analysis – integration testing – permission testing 4. Only manual code review by developers 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. Why is the misconception that official plugin stores are safe dangerous? 1. Store plugins are reviewed by security experts for weeks 2. Only unofficial stores contain malicious plugins 3. Store review is limited and imperfect – malicious plugins have passed initial review 4. Official stores use perfect automated scanning Correct! Why: Plugin store review is limited and imperfect – malicious plugins have been discovered in official stores after passing initial review. Context: Store presence is not security certification so organizations must still conduct their own vetting. Remember: Store approval does not equal security. 3 / 7 3. What guidance does the article give for Anthropic Claude MCP security? 1. Use only public MCP endpoints for convenience 2. Allow all MCP tools without restriction 3. Host MCP servers internally – authenticate via mTLS or API keys – monitor unusual tool sequences 4. Disable MCP entirely as it cannot be secured 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. 4 / 7 4. What does OWASP recommend regarding how plugins should be treated? 1. Disable all plugins by default with no exceptions 2. Treat plugins as untrusted with strict input validation and least privilege 3. Only use plugins developed in-house 4. Trust all plugins from official marketplaces Correct! Why: OWASP recommends treating plugins as untrusted while implementing strict input validation and applying least privilege. Context: This defensive posture acknowledges that plugins may be malicious or vulnerable and limits potential damage. Remember: Untrusted until proven otherwise. 5 / 7 5. What is OWASP LLM #7 and why does it exist? 1. Insecure Plugin Design – exists because plugin security is systematically weak across the industry 2. A certification standard for secure plugin development 3. An encryption protocol for plugin communications 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. 6 / 7 6. How can prompt injection lead to plugin abuse according to the article? 1. Prompt injection requires physical access to the plugin server 2. Hidden instructions in content cause the AI to misuse legitimate plugins for unintended actions 3. Plugins are immune to prompt injection attacks 4. Prompt injection only affects the AI response text not plugin behavior 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. 7 / 7 7. What are the three main plugin threat vectors identified in the article? 1. Network attacks – application attacks – physical attacks 2. Malicious plugins – compromised plugins – exploited plugins via prompt injection 3. Encryption – hashing – tokenization 4. Authentication – authorization – accounting 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. 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.
