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. Antivirus scanning of plugin files 2. Only manual code review by developers 3. Static analysis – dynamic analysis – integration testing – permission testing 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. Why is the misconception that official plugin stores are safe dangerous? 1. Store review is limited and imperfect – malicious plugins have passed initial review 2. Official stores use perfect automated scanning 3. Only unofficial stores contain malicious plugins 4. Store plugins are reviewed by security experts for weeks 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. Allow all MCP tools without restriction 2. Disable MCP entirely as it cannot be secured 3. Host MCP servers internally – authenticate via mTLS or API keys – monitor unusual tool sequences 4. Use only public MCP endpoints for convenience 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 fail-safe mechanisms does the article recommend for plugin containment? 1. Only manual review of each plugin action 2. Complete isolation with no network access 3. Rate limits – maximum actions per session – time-bound execution – automatic disablement on anomaly 4. Weekly security audits by external consultants Correct! Why: The article recommends rate limits on invocations plus maximum allowed actions per session plus time-bound execution windows plus automatic plugin disablement on anomaly detection. Context: These mechanisms prevent catastrophic damage even when plugins are compromised. Remember: Limit – Cap – Time-bound – Auto-disable. 5 / 7 5. What does OWASP recommend regarding how plugins should be treated? 1. Only use plugins developed in-house 2. Trust all plugins from official marketplaces 3. Treat plugins as untrusted with strict input validation and least privilege 4. Disable all plugins by default with no exceptions 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. 6 / 7 6. What is OWASP LLM #7 and why does it exist? 1. A certification standard for secure plugin development 2. An encryption protocol for plugin communications 3. A specific type of malware that targets AI systems 4. Insecure Plugin Design – exists because plugin security is systematically weak across the industry 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. 7 / 7 7. What is typosquatting in the context of plugin security? 1. Using keyboard shortcuts to bypass security 2. Creating plugins with names similar to popular ones hoping users install the wrong one 3. Encrypting plugin communications with weak algorithms 4. Typing commands incorrectly into the AI system 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. 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.
