chore(aaif): rename a bunch of repository references (#8152)
Signed-off-by: Michael Neale <michael.neale@gmail.com> Co-authored-by: Michael Neale <michael.neale@gmail.com> continuing migration to aaif
This commit is contained in:
@@ -27,7 +27,7 @@ These checks provide a safeguard, not a guarantee. They detect known patterns bu
|
||||
|
||||
When enabled, goose uses a multi-layered approach to detect threats before they run:
|
||||
|
||||
1. **Tool call is intercepted and analyzed** - When goose prepares to execute a tool, the security system extracts the tool parameter text and checks it against [threat patterns](https://github.com/block/goose/blob/main/crates/goose/src/security/patterns.rs). If ML-based detection is enabled, it also uses machine learning to analyze the semantic content of the tool call and recent conversation messages to better understand context and reduce false positives.
|
||||
1. **Tool call is intercepted and analyzed** - When goose prepares to execute a tool, the security system extracts the tool parameter text and checks it against [threat patterns](https://github.com/aaif-goose/goose/blob/main/crates/goose/src/security/patterns.rs). If ML-based detection is enabled, it also uses machine learning to analyze the semantic content of the tool call and recent conversation messages to better understand context and reduce false positives.
|
||||
2. **Risk is assessed** - Detected threats are assigned confidence scores
|
||||
3. **Execution pauses** - Threats that exceed your configured threshold need your decision
|
||||
4. **Security alert appears** - The alert displays the confidence level, a description of the finding, and a unique finding ID. For example:
|
||||
|
||||
Reference in New Issue
Block a user