SECAI Core · phase 5 of 15
Plugins
Additions that help tailor the software product to more closely match the infrastructure being managed from one organization to another.
The Explain card
- Plain English
- Plugins are add-on components that extend a software product so it fits a particular organisation's infrastructure, adding integrations and capabilities the core product does not ship with.
- Example
- A chat assistant gains a plugin that reads the company's ticketing system. It is convenient, until a crafted ticket contains hidden instructions, the model reads them through the plugin, and starts acting on an attacker's text as if it were the user's request.
- Why it matters
- Each plugin is new code, new permissions and a new data path into the model. Defenders must vet who wrote it, what it can reach, and what it can be tricked into doing.
- Hook
- A plugin is a door you installed yourself; make sure it is not a back door.
Where it sits in the deck
Phase 5: Interacting with Models: Prompting, APIs, and Retrieval
With a working model and clean data, learn the interaction layer — how users and systems communicate instructions and retrieve grounded answers.
