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. According to the article – why is the misconception that plugins just read data not harmful dangerous? 1. Many plugins have write and execute capabilities and even read-only plugins can exfiltrate data 2. Reading data requires special permissions that are never granted 3. Data exfiltration is impossible through plugin architecture 4. All plugins are strictly read-only by default Correct! Why: Many plugins have write and execute capabilities and even read-only plugins can exfiltrate sensitive data – read access to the wrong data is still a breach. Context: The assumption that reading is harmless ignores both hidden capabilities and data sensitivity. Remember: Read access to secrets is still a breach. 2 / 7 2. What security testing framework does the article recommend before approving plugins? 1. Only manual code review by developers 2. User acceptance testing in production 3. Antivirus scanning of plugin files 4. Static analysis – dynamic analysis – integration testing – permission testing 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. 3 / 7 3. Why is the misconception that official plugin stores are safe dangerous? 1. Official stores use perfect automated scanning 2. Only unofficial stores contain malicious plugins 3. Store review is limited and imperfect – malicious plugins have passed initial review 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. 4 / 7 4. What guidance does the article give for Anthropic Claude MCP security? 1. Disable MCP entirely as it cannot be secured 2. Allow all MCP tools without restriction 3. Use only public MCP endpoints for convenience 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. 5 / 7 5. According to the article – what approach is better for plugin security? 1. Equal numbers of plugins regardless of permissions 2. Fewer plugins with tight permissions rather than many plugins with broad access 3. Many plugins with broad access for maximum functionality 4. Only plugins that require administrator approval Correct! Why: The article states that fewer plugins with tight permissions is better security than many plugins with broad access. Context: Each unnecessary plugin or permission is potential exposure – enabling all plugins for convenience means maximum attack surface. Remember: Less is more for plugin security. 6 / 7 6. What are the three main plugin threat vectors identified in the article? 1. Malicious plugins – compromised plugins – exploited plugins via prompt injection 2. Authentication – authorization – accounting 3. Encryption – hashing – tokenization 4. Network attacks – application attacks – physical attacks 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 are always less secure than AI plugins 2. Traditional integrations cannot connect to external systems 3. AI plugins require more bandwidth than traditional integrations 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.
