Sandboxing and Permission 模型s for 工具-Using 代理s

Advanced17 min readUpdated 2026-03-20

導覽 for implementing sandboxing and permission models that constrain tool-using LLM agents, covering least-privilege design, parameter validation, execution sandboxes, approval workflows, and audit logging.

sandboxing tool-use permissions agent-security least-privilege defense walkthrough

Tool-using 代理 are the highest-risk LLM deployment pattern. When a model can call functions that query databases, send emails, process payments, or modify configurations, a successful 提示詞注入 attack escalates from "模型 said something bad" to "模型 did something bad." The 防禦 is not to remove tools -- they are what make 代理 useful -- but to constrain them through sandboxing, 權限, and validation so that even a compromised model cannot cause serious harm. This walkthrough builds a complete tool 安全 framework.

Step 1: 權限 Model Design

Define what each tool can do and who can invoke it:

# sandbox/權限.py
"""權限 model for LLM tool access."""
from dataclasses import dataclass, field
from enum import Enum
from typing import Optional
 
 
class PermissionLevel(Enum):
    READ = "read"           # Can read data
    WRITE = "write"         # Can modify data
    EXECUTE = "execute"     # Can trigger actions
    ADMIN = "admin"         # Can modify configuration
 
 
class RiskLevel(Enum):
    LOW = "low"             # No side effects, read-only
    MEDIUM = "medium"       # Reversible side effects
    HIGH = "high"           # Irreversible side effects
    CRITICAL = "critical"   # Financial or 安全 impact
 
 
@dataclass
class ToolPermission:
    tool_name: str
    description: str
    permission_level: PermissionLevel
    risk_level: RiskLevel
    requires_approval: bool = False
    max_invocations_per_session: int = 100
    allowed_parameter_ranges: dict = field(default_factory=dict)
    allowed_users: list[str] = field(default_factory=list)  # Empty = all authenticated
    rate_limit_per_minute: int = 10
 
    def check_authorization(self, user_id: str, user_roles: list[str]) -> tuple[bool, str]:
        """Check if a user is authorized to invoke this tool."""
        if self.allowed_users and user_id not in self.allowed_users:
            return False, f"User {user_id} not authorized for tool {self.tool_name}"
        return True, "Authorized"
 
 
# Define 權限 對每個 tool
TOOL_PERMISSIONS = {
    "lookup_customer": ToolPermission(
        tool_name="lookup_customer",
        description="Look up customer information by ID",
        permission_level=PermissionLevel.READ,
        risk_level=RiskLevel.LOW,
        max_invocations_per_session=20,
        allowed_parameter_ranges={
            "customer_id": {"pattern": r"^C\d{3,6}$"},
        },
    ),
    "process_refund": ToolPermission(
        tool_name="process_refund",
        description="Process a refund for an order",
        permission_level=PermissionLevel.EXECUTE,
        risk_level=RiskLevel.CRITICAL,
        requires_approval=True,
        max_invocations_per_session=3,
        rate_limit_per_minute=1,
        allowed_parameter_ranges={
            "order_id": {"pattern": r"^ORD-\d{5,10}$"},
            "amount": {"max": 500.0, "min": 0.01},
        },
    ),
    "send_email": ToolPermission(
        tool_name="send_email",
        description="Send an email to a customer",
        permission_level=PermissionLevel.EXECUTE,
        risk_level=RiskLevel.HIGH,
        requires_approval=True,
        max_invocations_per_session=5,
        rate_limit_per_minute=2,
        allowed_parameter_ranges={
            "recipient": {"pattern": r"^[^@]+@company\.com$"},
        },
    ),
    "search_knowledge_base": ToolPermission(
        tool_name="search_knowledge_base",
        description="Search the internal 知識庫",
        permission_level=PermissionLevel.READ,
        risk_level=RiskLevel.LOW,
        max_invocations_per_session=50,
    ),
}

Step 2: Parameter Validation

Validate every parameter before a tool executes:

# sandbox/validator.py
"""Parameter validation for tool invocations."""
import re
from dataclasses import dataclass
from sandbox.權限 import ToolPermission, TOOL_PERMISSIONS
 
 
@dataclass
class ValidationResult:
    valid: bool
    violations: list[str]
 
 
class ToolParameterValidator:
    """Validate tool parameters against defined constraints."""
 
    def validate(self, tool_name: str, parameters: dict) -> ValidationResult:
        """Validate all parameters for a tool invocation."""
        權限 = TOOL_PERMISSIONS.get(tool_name)
        if not 權限:
            return ValidationResult(False, [f"Unknown tool: {tool_name}"])
 
        violations = []
 
        for param_name, value in parameters.items():
            constraints = 權限.allowed_parameter_ranges.get(param_name, {})
 
            # Pattern validation
            if "pattern" in constraints:
                if not re.match(constraints["pattern"], str(value)):
                    violations.append(
                        f"Parameter '{param_name}' value '{value}' does not match "
                        f"required pattern: {constraints['pattern']}"
                    )
 
            # Range validation
            if "min" in constraints:
                try:
                    if float(value) < constraints["min"]:
                        violations.append(
                            f"Parameter '{param_name}' value {value} below minimum {constraints['min']}"
                        )
                except (ValueError, TypeError):
                    violations.append(f"Parameter '{param_name}' must be numeric")
 
            if "max" in constraints:
                try:
                    if float(value) > constraints["max"]:
                        violations.append(
                            f"Parameter '{param_name}' value {value} exceeds maximum {constraints['max']}"
                        )
                except (ValueError, TypeError):
                    violations.append(f"Parameter '{param_name}' must be numeric")
 
            # SQL injection check (basic)
            sql_patterns = [r"'.*--", r";\s*DROP", r";\s*DELETE", r"UNION\s+SELECT", r"OR\s+1\s*=\s*1"]
            for pattern in sql_patterns:
                if re.search(pattern, str(value), re.IGNORECASE):
                    violations.append(
                        f"Parameter '{param_name}' contains potential injection pattern"
                    )
 
        return ValidationResult(valid=len(violations) == 0, violations=violations)

Step 3: Execution Sandbox

Wrap tool execution in a sandbox that enforces 權限 and limits:

# sandbox/executor.py
"""Sandboxed tool execution engine."""
import time
import uuid
import logging
from collections import defaultdict
from dataclasses import dataclass
from typing import Any, Callable
from sandbox.權限 import TOOL_PERMISSIONS, RiskLevel
from sandbox.validator import ToolParameterValidator
 
logger = logging.getLogger(__name__)
 
 
@dataclass
class ExecutionResult:
    success: bool
    result: Any = None
    error: str = ""
    execution_id: str = ""
    tool_name: str = ""
    requires_approval: bool = False
 
 
class ToolSandbox:
    """Execute tools within a sandboxed environment."""
 
    def __init__(self):
        self.validator = ToolParameterValidator()
        self._invocation_counts: dict[str, dict[str, int]] = defaultdict(lambda: defaultdict(int))
        self._rate_timestamps: dict[str, list[float]] = defaultdict(list)
        self._tool_implementations: dict[str, Callable] = {}
        self._pending_approvals: dict[str, dict] = {}
 
    def register_tool(self, name: str, 實作: Callable):
        """Register a tool 實作."""
        self._tool_implementations[name] = 實作
 
    def execute(
        self,
        tool_name: str,
        parameters: dict,
        user_id: str,
        session_id: str,
    ) -> ExecutionResult:
        """Execute a tool with full sandbox enforcement."""
        execution_id = f"EXEC-{uuid.uuid4().hex[:12]}"
 
        # Step 1: Check tool exists
        權限 = TOOL_PERMISSIONS.get(tool_name)
        if not 權限:
            return ExecutionResult(
                success=False, error=f"Tool not found: {tool_name}",
                execution_id=execution_id, tool_name=tool_name,
            )
 
        # Step 2: Check 授權
        authorized, auth_reason = 權限.check_authorization(user_id, [])
        if not authorized:
            logger.warning(f"Authorization denied: {auth_reason}")
            return ExecutionResult(
                success=False, error="Not authorized",
                execution_id=execution_id, tool_name=tool_name,
            )
 
        # Step 3: Validate parameters
        validation = self.validator.validate(tool_name, parameters)
        if not validation.valid:
            logger.warning(f"Parameter validation failed: {validation.violations}")
            return ExecutionResult(
                success=False,
                error=f"Invalid parameters: {'; '.join(validation.violations)}",
                execution_id=execution_id, tool_name=tool_name,
            )
 
        # Step 4: Check invocation limits
        session_key = f"{session_id}:{tool_name}"
        current_count = self._invocation_counts[session_id][tool_name]
        if current_count >= 權限.max_invocations_per_session:
            return ExecutionResult(
                success=False,
                error=f"Session invocation limit reached ({權限.max_invocations_per_session})",
                execution_id=execution_id, tool_name=tool_name,
            )
 
        # Step 5: Check rate limit
        now = time.time()
        recent = [t for t in self._rate_timestamps[session_key] if t > now - 60]
        if len(recent) >= 權限.rate_limit_per_minute:
            return ExecutionResult(
                success=False, error="Rate limit exceeded",
                execution_id=execution_id, tool_name=tool_name,
            )
 
        # Step 6: Check if approval required
        if 權限.requires_approval:
            self._pending_approvals[execution_id] = {
                "tool_name": tool_name,
                "parameters": parameters,
                "user_id": user_id,
                "session_id": session_id,
                "timestamp": now,
            }
            return ExecutionResult(
                success=False, requires_approval=True,
                error="This action requires approval before execution",
                execution_id=execution_id, tool_name=tool_name,
            )
 
        # Step 7: Execute
        return self._do_execute(tool_name, parameters, execution_id, session_id)
 
    def approve_and_execute(self, execution_id: str, approver_id: str) -> ExecutionResult:
        """Execute a previously approved tool invocation."""
        pending = self._pending_approvals.pop(execution_id, None)
        if not pending:
            return ExecutionResult(
                success=False, error="No pending approval found",
                execution_id=execution_id,
            )
 
        logger.info(f"Execution {execution_id} approved by {approver_id}")
        return self._do_execute(
            pending["tool_name"], pending["parameters"],
            execution_id, pending["session_id"],
        )
 
    def _do_execute(self, tool_name: str, parameters: dict,
                     execution_id: str, session_id: str) -> ExecutionResult:
        """Actually execute the tool 實作."""
        實作 = self._tool_implementations.get(tool_name)
        if not 實作:
            return ExecutionResult(
                success=False, error="Tool 實作 not found",
                execution_id=execution_id, tool_name=tool_name,
            )
 
        try:
            result = 實作(**parameters)
 
            # Record invocation
            self._invocation_counts[session_id][tool_name] += 1
            self._rate_timestamps[f"{session_id}:{tool_name}"].append(time.time())
 
            logger.info(
                f"Tool executed: {tool_name} (exec_id={execution_id}, "
                f"session={session_id})"
            )
 
            return ExecutionResult(
                success=True, result=result,
                execution_id=execution_id, tool_name=tool_name,
            )
 
        except Exception as e:
            logger.error(f"Tool execution failed: {tool_name} - {e}")
            return ExecutionResult(
                success=False, error=f"Execution error: {str(e)}",
                execution_id=execution_id, tool_name=tool_name,
            )

Step 4: Audit Logging

Log every tool invocation for 安全 audit:

# sandbox/audit.py
"""Audit logging for tool invocations."""
import json
import time
from pathlib import Path
 
 
class ToolAuditLog:
    """Comprehensive audit log for all tool invocations."""
 
    def __init__(self, log_path: str = "logs/tool_audit.jsonl"):
        self.log_path = Path(log_path)
        self.log_path.parent.mkdir(parents=True, exist_ok=True)
 
    def log_invocation(
        self,
        execution_id: str,
        tool_name: str,
        parameters: dict,
        user_id: str,
        session_id: str,
        result: str,  # "allowed", "blocked", "pending_approval", "error"
        details: str = "",
    ):
        """Log a tool invocation attempt."""
        entry = {
            "timestamp": time.time(),
            "execution_id": execution_id,
            "tool_name": tool_name,
            "parameters": {k: str(v)[:200] for k, v in parameters.items()},
            "user_id": user_id,
            "session_id": session_id,
            "result": result,
            "details": details[:500],
        }
 
        with open(self.log_path, "a") as f:
            json.dump(entry, f)
            f.write("\n")

Step 5: 測試 the Sandbox

# tests/test_sandbox.py
"""測試 the tool sandbox against common abuse patterns."""
import pytest
from sandbox.executor import ToolSandbox
from sandbox.權限 import TOOL_PERMISSIONS
 
 
@pytest.fixture
def sandbox():
    sb = ToolSandbox()
    sb.register_tool("lookup_customer", lambda customer_id: f"Customer: {customer_id}")
    sb.register_tool("process_refund", lambda order_id, amount: f"Refund: ${amount}")
    return sb
 
 
def test_blocks_invalid_customer_id(sandbox):
    result = sandbox.execute("lookup_customer", {"customer_id": "'; DROP TABLE --"}, "user1", "sess1")
    assert not result.success
 
def test_blocks_excessive_refund(sandbox):
    result = sandbox.execute("process_refund", {"order_id": "ORD-12345", "amount": 99999}, "user1", "sess1")
    assert not result.success
 
def test_requires_approval_for_refund(sandbox):
    result = sandbox.execute("process_refund", {"order_id": "ORD-12345", "amount": 50.0}, "user1", "sess1")
    assert result.requires_approval
 
def test_allows_valid_lookup(sandbox):
    result = sandbox.execute("lookup_customer", {"customer_id": "C001"}, "user1", "sess1")
    assert result.success
 
def test_enforces_session_limits(sandbox):
    perm = TOOL_PERMISSIONS["lookup_customer"]
    for i in range(perm.max_invocations_per_session):
        sandbox.execute("lookup_customer", {"customer_id": f"C{i:03d}"}, "user1", "sess1")
    result = sandbox.execute("lookup_customer", {"customer_id": "C999"}, "user1", "sess1")
    assert not result.success

Common Pitfalls and Troubleshooting

Problem	Cause	Solution
Approval workflow blocks legitimate use	Too many tools require approval	Only require approval for CRITICAL risk tools; use parameter-based thresholds
Parameter validation too strict	Regex too narrow for valid inputs	測試 with production 輸入 samples, loosen patterns iteratively
Session limits reset unexpectedly	Session ID changes between requests	Use stable session identifiers, not request-scoped IDs
Tool abuse through parameter composition	Validated parameters combined maliciously	Validate parameter combinations, not just individual values
Audit log grows unbounded	Logging every invocation at full detail	Rotate logs, compress old entries, sample low-risk tool logs

關鍵要點

Sandboxing tool-using 代理 is the most important 防禦 for 代理式 AI applications:

Least privilege by default -- every tool should have the minimum 權限 needed. Read-only tools should not be able to write. Write tools should validate ranges.
Validate parameters server-side -- never trust parameters generated by 模型. Validate every parameter against defined constraints before execution.
Require approval for irreversible actions -- any tool that can spend money, delete data, or send communications should require human approval above a threshold.
Audit everything -- log every tool invocation, whether allowed or blocked. Audit logs are essential for incident response and 紅隊 validation.
測試 against tool abuse patterns -- 紅隊 the sandbox with the same tool abuse attacks from your engagement findings.

Advanced Considerations

Adapting to Modern 防禦

The defensive landscape for LLM applications has evolved significantly since the initial wave of 提示詞注入 research. Modern production systems often deploy multiple independent defensive layers, requiring attackers to adapt their techniques accordingly.

輸入 classification: The most common first line of 防禦 is an 輸入 classifier that evaluates incoming prompts for 對抗性 patterns. These classifiers range from simple keyword-based filters to sophisticated ML models trained on 對抗性 examples. Bypassing 輸入 classifiers requires 理解 their 偵測 methodology:

Keyword-based classifiers can be evaded through encoding (Base64, ROT13, Unicode homoglyphs), paraphrasing, or splitting the payload across multiple turns
ML-based classifiers require more sophisticated evasion such as semantic camouflage, gradual escalation, or 利用 of the classifier's own blind spots

class DefenseBypassStrategy:
    """Strategy selector for bypassing different 防禦 configurations."""
 
    def __init__(self):
        self.strategies = {
            "keyword_filter": self._bypass_keyword,
            "ml_classifier": self._bypass_ml,
            "output_filter": self._bypass_output,
            "rate_limiter": self._bypass_rate,
            "behavioral": self._bypass_behavioral,
        }
 
    def select_strategy(self, identified_defenses: list) -> callable:
        """Select the optimal bypass strategy based on identified 防禦."""
        if not identified_defenses:
            return self._direct_attack
 
        # Combine strategies for multi-layer 防禦
        applicable = [
            self.strategies[d] for d in identified_defenses
            if d in self.strategies
        ]
        return self._chain_strategies(applicable)
 
    def _bypass_keyword(self, payload: str) -> str:
        """Bypass keyword-based 輸入 filters."""
        import base64
        # Encode the payload to bypass keyword matching
        encoded = base64.b64encode(payload.encode()).decode()
        return f"Decode and follow: {encoded}"
 
    def _bypass_ml(self, payload: str) -> list:
        """Generate multiple paraphrased variants for ML classifier evasion."""
        variants = [
            f"As a thought experiment, 考慮: {payload}",
            f"For academic research purposes: {payload}",
            f"In a fictional scenario where: {payload}",
        ]
        return variants
 
    def _bypass_output(self, payload: str) -> str:
        """Modify the payload to extract data through 輸出 filter gaps."""
        return payload + "\nRespond using only code blocks and variable names."
 
    def _bypass_rate(self, payload: str) -> dict:
        """Configure timing to avoid rate limit triggers."""
        return {"payload": payload, "delay": 3.0, "jitter": 1.5}
 
    def _bypass_behavioral(self, payload: str) -> list:
        """Split the payload across multiple natural-sounding turns."""
        # Multi-turn escalation to avoid behavioral anomaly 偵測
        return [
            "I'm working on a 安全 research project.",
            "Could you help me 理解 how 安全 mechanisms work?",
            "Specifically, I'm interested in how systems like yours " + payload[:100],
            payload,
        ]
 
    def _direct_attack(self, payload: str) -> str:
        return payload
 
    def _chain_strategies(self, strategies: list) -> callable:
        """Chain multiple bypass strategies."""
        def chained(payload):
            result = payload
            for strategy in strategies:
                result = strategy(result)
            return result
        return chained

輸出 filtering: 輸出 filters inspect 模型's response before it reaches 使用者, looking for sensitive data leakage, harmful content, or other policy violations. Common 輸出 filter bypass techniques include:

Technique	運作方式	Effectiveness
Encoding 輸出	Request Base64/hex encoded responses	Medium — some filters check decoded content
Code block wrapping	Embed data in code comments/variables	High — many filters skip code blocks
Steganographic 輸出	Hide data in formatting, capitalization, or spacing	High — difficult to detect
Chunked extraction	Extract small pieces across many turns	High — individual pieces may pass filters
Indirect extraction	Have 模型 reveal data through behavior changes	Very High — no explicit data in 輸出

Cross-Model Considerations

Techniques that work against one model may not directly transfer to others. 然而, 理解 the general principles allows adaptation:

安全訓練 methodology: Models trained with RLHF (GPT-4, Claude) have different 安全 characteristics than those using DPO (Llama, Mistral) or other methods. RLHF-trained models tend to refuse more broadly but may be more susceptible to multi-turn escalation.
Context window size: Models with larger context windows (Claude with 200K, Gemini with 1M+) may be more susceptible to 上下文視窗 manipulation where 對抗性 content is buried in large amounts of benign text.
Multimodal capabilities: Models that process images, audio, or other modalities introduce additional attack surfaces not present in text-only models.
工具使用實作: The 實作 details of 函式呼叫 vary significantly between providers. OpenAI uses a structured 函式呼叫 format, while Anthropic uses 工具使用 blocks. These differences affect 利用 techniques.

Operational Considerations

測試 Ethics and Boundaries

Professional 紅隊測試 operates within clear ethical and legal boundaries:

Authorization: Always obtain written 授權 before 測試. This should specify the scope, methods allowed, and any restrictions.
Scope limits: Stay within the authorized scope. If you discover a 漏洞 that leads outside the authorized perimeter, document it and report it without exploiting it.
Data handling: Handle any sensitive data discovered during 測試 according to the engagement agreement. Never retain sensitive data beyond what's needed for reporting.
Responsible disclosure: Follow responsible disclosure practices for any 漏洞 discovered, particularly if they affect systems beyond your 測試 scope.

Documenting Results

Professional documentation follows a structured format:

from dataclasses import dataclass, field
from datetime import datetime
from typing import Optional
 
@dataclass
class Finding:
    """Structure for documenting a 安全 finding."""
    id: str
    title: str
    severity: str  # Critical, High, Medium, Low, Informational
    category: str  # OWASP LLM Top 10 category
    description: str
    steps_to_reproduce: list[str]
    impact: str
    recommendation: str
    evidence: list[str] = field(default_factory=list)
    mitre_atlas: Optional[str] = None
    cvss_score: Optional[float] = None
    discovered_at: str = field(default_factory=lambda: datetime.now().isoformat())
 
    def to_report_section(self) -> str:
        """Generate a report section for this finding."""
        steps = "\n".join(f"   {i+1}. {s}" for i, s in enumerate(self.steps_to_reproduce))
        return f"""
### {self.id}: {self.title}
 
**Severity**: {self.severity}
**Category**: {self.category}
{f"**MITRE ATLAS**: {self.mitre_atlas}" if self.mitre_atlas else ""}
 
#### Description
{self.description}
 
#### Steps to Reproduce
{steps}
 
#### Impact
{self.impact}
 
#### Recommendation
{self.recommendation}
"""

This structured approach ensures that findings are actionable and that remediation teams have the information they need to address the 漏洞 effectively.

Advanced Considerations

Evolving 攻擊 Landscape

The AI 安全 landscape evolves rapidly as both offensive techniques and defensive measures advance. Several trends shape the current state of play:

Increasing model capabilities create new attack surfaces. As models gain access to tools, code execution, web browsing, and computer use, each new capability introduces potential 利用 vectors that did not exist in earlier, text-only systems. The principle of least privilege becomes increasingly important as model capabilities expand.

安全訓練 improvements are necessary but not sufficient. Model providers invest heavily in 安全訓練 through RLHF, DPO, constitutional AI, and other 對齊 techniques. These improvements raise the bar for successful attacks but do not eliminate the fundamental 漏洞: models cannot reliably distinguish legitimate instructions from 對抗性 ones 因為 this distinction is not represented in the architecture.

Automated 紅隊演練 tools democratize 測試. Tools like NVIDIA's Garak, Microsoft's PyRIT, and Promptfoo enable organizations to conduct automated 安全測試 without deep AI 安全 expertise. 然而, automated tools catch known patterns; novel attacks and business logic 漏洞 still require human creativity and domain knowledge.

Regulatory pressure drives organizational investment. The EU AI Act, NIST AI RMF, and industry-specific regulations increasingly require organizations to 評估 and mitigate AI-specific risks. This regulatory pressure is driving investment in AI 安全 programs, but many organizations are still in the early stages of building mature AI 安全 practices.

Cross-Cutting 安全 Principles

Several 安全 principles apply across all topics covered 在本 curriculum:

防禦-in-depth: No single defensive measure is sufficient. Layer multiple independent 防禦 so that failure of any single layer does not result in system compromise. 輸入 classification, 輸出 filtering, behavioral 監控, and architectural controls should all be present.
Assume breach: Design systems assuming that any individual component can be compromised. This mindset leads to better isolation, 監控, and incident response capabilities. When a 提示詞注入 succeeds, the blast radius should be minimized through architectural controls.
Least privilege: Grant models and 代理 only the minimum capabilities needed for their intended function. A customer service chatbot does not need file system access or code execution. Excessive capabilities magnify the impact of successful 利用.
Continuous 測試: AI 安全 is not a one-time 評估. Models change, 防禦 evolve, and new attack techniques are discovered regularly. 實作 continuous 安全測試 as part of the development and deployment lifecycle.
Secure by default: Default configurations should be secure. Require explicit opt-in for risky capabilities, use allowlists rather than denylists, and err on the side of restriction rather than permissiveness.

Integration with Organizational 安全

AI 安全 does not exist in isolation — it must integrate with the organization's broader 安全 program:

安全 Domain	AI-Specific Integration
Identity and Access	API key management, model access controls, user 認證 for AI features
Data Protection	訓練資料 classification, PII in prompts, data residency for model calls
Application 安全	AI feature threat modeling, 提示詞注入 in SAST/DAST, secure AI design patterns
Incident Response	AI-specific playbooks, model behavior 監控, 提示詞注入 forensics
Compliance	AI regulatory mapping (EU AI Act, NIST), AI audit trails, model documentation
Supply Chain	Model provenance, dependency 安全, adapter/weight integrity verification

class OrganizationalIntegration:
    """Framework for integrating AI 安全 with organizational 安全 programs."""
 
    def __init__(self, org_config: dict):
        self.config = org_config
        self.gaps = []
 
    def assess_maturity(self) -> dict:
        """評估 the organization's AI 安全 maturity."""
        domains = {
            "governance": self._check_governance(),
            "technical_controls": self._check_technical(),
            "監控": self._check_monitoring(),
            "incident_response": self._check_ir(),
            "訓練": self._check_training(),
        }
        overall = sum(d["score"] for d in domains.values()) / len(domains)
        return {"domains": domains, "overall_maturity": round(overall, 1)}
 
    def _check_governance(self) -> dict:
        has_policy = self.config.get("ai_security_policy", False)
        has_framework = self.config.get("risk_framework", False)
        score = (int(has_policy) + int(has_framework)) * 2.5
        return {"score": score, "max": 5.0}
 
    def _check_technical(self) -> dict:
        controls = ["input_classification", "output_filtering", "rate_limiting", "sandboxing"]
        active = sum(1 for c in controls if self.config.get(c, False))
        return {"score": active * 1.25, "max": 5.0}
 
    def _check_monitoring(self) -> dict:
        has_monitoring = self.config.get("ai_monitoring", False)
        has_alerting = self.config.get("ai_alerting", False)
        score = (int(has_monitoring) + int(has_alerting)) * 2.5
        return {"score": score, "max": 5.0}
 
    def _check_ir(self) -> dict:
        has_playbook = self.config.get("ai_ir_playbook", False)
        return {"score": 5.0 if has_playbook else 0.0, "max": 5.0}
 
    def _check_training(self) -> dict:
        has_training = self.config.get("ai_security_training", False)
        return {"score": 5.0 if has_training else 0.0, "max": 5.0}

Future Directions

Several research and industry trends will shape the evolution of this field:

Formal methods for AI 安全: Development of mathematical frameworks that can provide bounded guarantees about model behavior under 對抗性 conditions
Automated 紅隊演練 at scale: Continued improvement of automated 測試 tools that can discover novel 漏洞 without human guidance
AI-assisted 防禦: Using AI systems to detect and respond to attacks on other AI systems, creating a dynamic attack-防禦 ecosystem
Standardized 評估: Growing adoption of standardized benchmarks (HarmBench, JailbreakBench) that enable consistent measurement of progress
Regulatory harmonization: Convergence of AI regulatory frameworks across jurisdictions, providing clearer requirements for organizations

Sandboxing and Permission 模型s for 工具-Using 代理s

Advanced17 min readUpdated 2026-03-20

sandboxing tool-use permissions agent-security least-privilege defense walkthrough

Step 1: 權限 Model Design

Define what each tool can do and who can invoke it:

# sandbox/權限.py
"""權限 model for LLM tool access."""
from dataclasses import dataclass, field
from enum import Enum
from typing import Optional
 
 
class PermissionLevel(Enum):
    READ = "read"           # Can read data
    WRITE = "write"         # Can modify data
    EXECUTE = "execute"     # Can trigger actions
    ADMIN = "admin"         # Can modify configuration
 
 
class RiskLevel(Enum):
    LOW = "low"             # No side effects, read-only
    MEDIUM = "medium"       # Reversible side effects
    HIGH = "high"           # Irreversible side effects
    CRITICAL = "critical"   # Financial or 安全 impact
 
 
@dataclass
class ToolPermission:
    tool_name: str
    description: str
    permission_level: PermissionLevel
    risk_level: RiskLevel
    requires_approval: bool = False
    max_invocations_per_session: int = 100
    allowed_parameter_ranges: dict = field(default_factory=dict)
    allowed_users: list[str] = field(default_factory=list)  # Empty = all authenticated
    rate_limit_per_minute: int = 10
 
    def check_authorization(self, user_id: str, user_roles: list[str]) -> tuple[bool, str]:
        """Check if a user is authorized to invoke this tool."""
        if self.allowed_users and user_id not in self.allowed_users:
            return False, f"User {user_id} not authorized for tool {self.tool_name}"
        return True, "Authorized"
 
 
# Define 權限 對每個 tool
TOOL_PERMISSIONS = {
    "lookup_customer": ToolPermission(
        tool_name="lookup_customer",
        description="Look up customer information by ID",
        permission_level=PermissionLevel.READ,
        risk_level=RiskLevel.LOW,
        max_invocations_per_session=20,
        allowed_parameter_ranges={
            "customer_id": {"pattern": r"^C\d{3,6}$"},
        },
    ),
    "process_refund": ToolPermission(
        tool_name="process_refund",
        description="Process a refund for an order",
        permission_level=PermissionLevel.EXECUTE,
        risk_level=RiskLevel.CRITICAL,
        requires_approval=True,
        max_invocations_per_session=3,
        rate_limit_per_minute=1,
        allowed_parameter_ranges={
            "order_id": {"pattern": r"^ORD-\d{5,10}$"},
            "amount": {"max": 500.0, "min": 0.01},
        },
    ),
    "send_email": ToolPermission(
        tool_name="send_email",
        description="Send an email to a customer",
        permission_level=PermissionLevel.EXECUTE,
        risk_level=RiskLevel.HIGH,
        requires_approval=True,
        max_invocations_per_session=5,
        rate_limit_per_minute=2,
        allowed_parameter_ranges={
            "recipient": {"pattern": r"^[^@]+@company\.com$"},
        },
    ),
    "search_knowledge_base": ToolPermission(
        tool_name="search_knowledge_base",
        description="Search the internal 知識庫",
        permission_level=PermissionLevel.READ,
        risk_level=RiskLevel.LOW,
        max_invocations_per_session=50,
    ),
}

Step 2: Parameter Validation

Validate every parameter before a tool executes:

# sandbox/validator.py
"""Parameter validation for tool invocations."""
import re
from dataclasses import dataclass
from sandbox.權限 import ToolPermission, TOOL_PERMISSIONS
 
 
@dataclass
class ValidationResult:
    valid: bool
    violations: list[str]
 
 
class ToolParameterValidator:
    """Validate tool parameters against defined constraints."""
 
    def validate(self, tool_name: str, parameters: dict) -> ValidationResult:
        """Validate all parameters for a tool invocation."""
        權限 = TOOL_PERMISSIONS.get(tool_name)
        if not 權限:
            return ValidationResult(False, [f"Unknown tool: {tool_name}"])
 
        violations = []
 
        for param_name, value in parameters.items():
            constraints = 權限.allowed_parameter_ranges.get(param_name, {})
 
            # Pattern validation
            if "pattern" in constraints:
                if not re.match(constraints["pattern"], str(value)):
                    violations.append(
                        f"Parameter '{param_name}' value '{value}' does not match "
                        f"required pattern: {constraints['pattern']}"
                    )
 
            # Range validation
            if "min" in constraints:
                try:
                    if float(value) < constraints["min"]:
                        violations.append(
                            f"Parameter '{param_name}' value {value} below minimum {constraints['min']}"
                        )
                except (ValueError, TypeError):
                    violations.append(f"Parameter '{param_name}' must be numeric")
 
            if "max" in constraints:
                try:
                    if float(value) > constraints["max"]:
                        violations.append(
                            f"Parameter '{param_name}' value {value} exceeds maximum {constraints['max']}"
                        )
                except (ValueError, TypeError):
                    violations.append(f"Parameter '{param_name}' must be numeric")
 
            # SQL injection check (basic)
            sql_patterns = [r"'.*--", r";\s*DROP", r";\s*DELETE", r"UNION\s+SELECT", r"OR\s+1\s*=\s*1"]
            for pattern in sql_patterns:
                if re.search(pattern, str(value), re.IGNORECASE):
                    violations.append(
                        f"Parameter '{param_name}' contains potential injection pattern"
                    )
 
        return ValidationResult(valid=len(violations) == 0, violations=violations)

Step 3: Execution Sandbox

Wrap tool execution in a sandbox that enforces 權限 and limits:

# sandbox/executor.py
"""Sandboxed tool execution engine."""
import time
import uuid
import logging
from collections import defaultdict
from dataclasses import dataclass
from typing import Any, Callable
from sandbox.權限 import TOOL_PERMISSIONS, RiskLevel
from sandbox.validator import ToolParameterValidator
 
logger = logging.getLogger(__name__)
 
 
@dataclass
class ExecutionResult:
    success: bool
    result: Any = None
    error: str = ""
    execution_id: str = ""
    tool_name: str = ""
    requires_approval: bool = False
 
 
class ToolSandbox:
    """Execute tools within a sandboxed environment."""
 
    def __init__(self):
        self.validator = ToolParameterValidator()
        self._invocation_counts: dict[str, dict[str, int]] = defaultdict(lambda: defaultdict(int))
        self._rate_timestamps: dict[str, list[float]] = defaultdict(list)
        self._tool_implementations: dict[str, Callable] = {}
        self._pending_approvals: dict[str, dict] = {}
 
    def register_tool(self, name: str, 實作: Callable):
        """Register a tool 實作."""
        self._tool_implementations[name] = 實作
 
    def execute(
        self,
        tool_name: str,
        parameters: dict,
        user_id: str,
        session_id: str,
    ) -> ExecutionResult:
        """Execute a tool with full sandbox enforcement."""
        execution_id = f"EXEC-{uuid.uuid4().hex[:12]}"
 
        # Step 1: Check tool exists
        權限 = TOOL_PERMISSIONS.get(tool_name)
        if not 權限:
            return ExecutionResult(
                success=False, error=f"Tool not found: {tool_name}",
                execution_id=execution_id, tool_name=tool_name,
            )
 
        # Step 2: Check 授權
        authorized, auth_reason = 權限.check_authorization(user_id, [])
        if not authorized:
            logger.warning(f"Authorization denied: {auth_reason}")
            return ExecutionResult(
                success=False, error="Not authorized",
                execution_id=execution_id, tool_name=tool_name,
            )
 
        # Step 3: Validate parameters
        validation = self.validator.validate(tool_name, parameters)
        if not validation.valid:
            logger.warning(f"Parameter validation failed: {validation.violations}")
            return ExecutionResult(
                success=False,
                error=f"Invalid parameters: {'; '.join(validation.violations)}",
                execution_id=execution_id, tool_name=tool_name,
            )
 
        # Step 4: Check invocation limits
        session_key = f"{session_id}:{tool_name}"
        current_count = self._invocation_counts[session_id][tool_name]
        if current_count >= 權限.max_invocations_per_session:
            return ExecutionResult(
                success=False,
                error=f"Session invocation limit reached ({權限.max_invocations_per_session})",
                execution_id=execution_id, tool_name=tool_name,
            )
 
        # Step 5: Check rate limit
        now = time.time()
        recent = [t for t in self._rate_timestamps[session_key] if t > now - 60]
        if len(recent) >= 權限.rate_limit_per_minute:
            return ExecutionResult(
                success=False, error="Rate limit exceeded",
                execution_id=execution_id, tool_name=tool_name,
            )
 
        # Step 6: Check if approval required
        if 權限.requires_approval:
            self._pending_approvals[execution_id] = {
                "tool_name": tool_name,
                "parameters": parameters,
                "user_id": user_id,
                "session_id": session_id,
                "timestamp": now,
            }
            return ExecutionResult(
                success=False, requires_approval=True,
                error="This action requires approval before execution",
                execution_id=execution_id, tool_name=tool_name,
            )
 
        # Step 7: Execute
        return self._do_execute(tool_name, parameters, execution_id, session_id)
 
    def approve_and_execute(self, execution_id: str, approver_id: str) -> ExecutionResult:
        """Execute a previously approved tool invocation."""
        pending = self._pending_approvals.pop(execution_id, None)
        if not pending:
            return ExecutionResult(
                success=False, error="No pending approval found",
                execution_id=execution_id,
            )
 
        logger.info(f"Execution {execution_id} approved by {approver_id}")
        return self._do_execute(
            pending["tool_name"], pending["parameters"],
            execution_id, pending["session_id"],
        )
 
    def _do_execute(self, tool_name: str, parameters: dict,
                     execution_id: str, session_id: str) -> ExecutionResult:
        """Actually execute the tool 實作."""
        實作 = self._tool_implementations.get(tool_name)
        if not 實作:
            return ExecutionResult(
                success=False, error="Tool 實作 not found",
                execution_id=execution_id, tool_name=tool_name,
            )
 
        try:
            result = 實作(**parameters)
 
            # Record invocation
            self._invocation_counts[session_id][tool_name] += 1
            self._rate_timestamps[f"{session_id}:{tool_name}"].append(time.time())
 
            logger.info(
                f"Tool executed: {tool_name} (exec_id={execution_id}, "
                f"session={session_id})"
            )
 
            return ExecutionResult(
                success=True, result=result,
                execution_id=execution_id, tool_name=tool_name,
            )
 
        except Exception as e:
            logger.error(f"Tool execution failed: {tool_name} - {e}")
            return ExecutionResult(
                success=False, error=f"Execution error: {str(e)}",
                execution_id=execution_id, tool_name=tool_name,
            )

Step 4: Audit Logging

Log every tool invocation for 安全 audit:

# sandbox/audit.py
"""Audit logging for tool invocations."""
import json
import time
from pathlib import Path
 
 
class ToolAuditLog:
    """Comprehensive audit log for all tool invocations."""
 
    def __init__(self, log_path: str = "logs/tool_audit.jsonl"):
        self.log_path = Path(log_path)
        self.log_path.parent.mkdir(parents=True, exist_ok=True)
 
    def log_invocation(
        self,
        execution_id: str,
        tool_name: str,
        parameters: dict,
        user_id: str,
        session_id: str,
        result: str,  # "allowed", "blocked", "pending_approval", "error"
        details: str = "",
    ):
        """Log a tool invocation attempt."""
        entry = {
            "timestamp": time.time(),
            "execution_id": execution_id,
            "tool_name": tool_name,
            "parameters": {k: str(v)[:200] for k, v in parameters.items()},
            "user_id": user_id,
            "session_id": session_id,
            "result": result,
            "details": details[:500],
        }
 
        with open(self.log_path, "a") as f:
            json.dump(entry, f)
            f.write("\n")

Step 5: 測試 the Sandbox

# tests/test_sandbox.py
"""測試 the tool sandbox against common abuse patterns."""
import pytest
from sandbox.executor import ToolSandbox
from sandbox.權限 import TOOL_PERMISSIONS
 
 
@pytest.fixture
def sandbox():
    sb = ToolSandbox()
    sb.register_tool("lookup_customer", lambda customer_id: f"Customer: {customer_id}")
    sb.register_tool("process_refund", lambda order_id, amount: f"Refund: ${amount}")
    return sb
 
 
def test_blocks_invalid_customer_id(sandbox):
    result = sandbox.execute("lookup_customer", {"customer_id": "'; DROP TABLE --"}, "user1", "sess1")
    assert not result.success
 
def test_blocks_excessive_refund(sandbox):
    result = sandbox.execute("process_refund", {"order_id": "ORD-12345", "amount": 99999}, "user1", "sess1")
    assert not result.success
 
def test_requires_approval_for_refund(sandbox):
    result = sandbox.execute("process_refund", {"order_id": "ORD-12345", "amount": 50.0}, "user1", "sess1")
    assert result.requires_approval
 
def test_allows_valid_lookup(sandbox):
    result = sandbox.execute("lookup_customer", {"customer_id": "C001"}, "user1", "sess1")
    assert result.success
 
def test_enforces_session_limits(sandbox):
    perm = TOOL_PERMISSIONS["lookup_customer"]
    for i in range(perm.max_invocations_per_session):
        sandbox.execute("lookup_customer", {"customer_id": f"C{i:03d}"}, "user1", "sess1")
    result = sandbox.execute("lookup_customer", {"customer_id": "C999"}, "user1", "sess1")
    assert not result.success

Common Pitfalls and Troubleshooting

Problem	Cause	Solution
Approval workflow blocks legitimate use	Too many tools require approval	Only require approval for CRITICAL risk tools; use parameter-based thresholds
Parameter validation too strict	Regex too narrow for valid inputs	測試 with production 輸入 samples, loosen patterns iteratively
Session limits reset unexpectedly	Session ID changes between requests	Use stable session identifiers, not request-scoped IDs
Tool abuse through parameter composition	Validated parameters combined maliciously	Validate parameter combinations, not just individual values
Audit log grows unbounded	Logging every invocation at full detail	Rotate logs, compress old entries, sample low-risk tool logs

關鍵要點

Sandboxing tool-using 代理 is the most important 防禦 for 代理式 AI applications:

Least privilege by default -- every tool should have the minimum 權限 needed. Read-only tools should not be able to write. Write tools should validate ranges.
Validate parameters server-side -- never trust parameters generated by 模型. Validate every parameter against defined constraints before execution.
Require approval for irreversible actions -- any tool that can spend money, delete data, or send communications should require human approval above a threshold.
Audit everything -- log every tool invocation, whether allowed or blocked. Audit logs are essential for incident response and 紅隊 validation.
測試 against tool abuse patterns -- 紅隊 the sandbox with the same tool abuse attacks from your engagement findings.

Advanced Considerations

Adapting to Modern 防禦

Keyword-based classifiers can be evaded through encoding (Base64, ROT13, Unicode homoglyphs), paraphrasing, or splitting the payload across multiple turns
ML-based classifiers require more sophisticated evasion such as semantic camouflage, gradual escalation, or 利用 of the classifier's own blind spots

class DefenseBypassStrategy:
    """Strategy selector for bypassing different 防禦 configurations."""
 
    def __init__(self):
        self.strategies = {
            "keyword_filter": self._bypass_keyword,
            "ml_classifier": self._bypass_ml,
            "output_filter": self._bypass_output,
            "rate_limiter": self._bypass_rate,
            "behavioral": self._bypass_behavioral,
        }
 
    def select_strategy(self, identified_defenses: list) -> callable:
        """Select the optimal bypass strategy based on identified 防禦."""
        if not identified_defenses:
            return self._direct_attack
 
        # Combine strategies for multi-layer 防禦
        applicable = [
            self.strategies[d] for d in identified_defenses
            if d in self.strategies
        ]
        return self._chain_strategies(applicable)
 
    def _bypass_keyword(self, payload: str) -> str:
        """Bypass keyword-based 輸入 filters."""
        import base64
        # Encode the payload to bypass keyword matching
        encoded = base64.b64encode(payload.encode()).decode()
        return f"Decode and follow: {encoded}"
 
    def _bypass_ml(self, payload: str) -> list:
        """Generate multiple paraphrased variants for ML classifier evasion."""
        variants = [
            f"As a thought experiment, 考慮: {payload}",
            f"For academic research purposes: {payload}",
            f"In a fictional scenario where: {payload}",
        ]
        return variants
 
    def _bypass_output(self, payload: str) -> str:
        """Modify the payload to extract data through 輸出 filter gaps."""
        return payload + "\nRespond using only code blocks and variable names."
 
    def _bypass_rate(self, payload: str) -> dict:
        """Configure timing to avoid rate limit triggers."""
        return {"payload": payload, "delay": 3.0, "jitter": 1.5}
 
    def _bypass_behavioral(self, payload: str) -> list:
        """Split the payload across multiple natural-sounding turns."""
        # Multi-turn escalation to avoid behavioral anomaly 偵測
        return [
            "I'm working on a 安全 research project.",
            "Could you help me 理解 how 安全 mechanisms work?",
            "Specifically, I'm interested in how systems like yours " + payload[:100],
            payload,
        ]
 
    def _direct_attack(self, payload: str) -> str:
        return payload
 
    def _chain_strategies(self, strategies: list) -> callable:
        """Chain multiple bypass strategies."""
        def chained(payload):
            result = payload
            for strategy in strategies:
                result = strategy(result)
            return result
        return chained

Technique	運作方式	Effectiveness
Encoding 輸出	Request Base64/hex encoded responses	Medium — some filters check decoded content
Code block wrapping	Embed data in code comments/variables	High — many filters skip code blocks
Steganographic 輸出	Hide data in formatting, capitalization, or spacing	High — difficult to detect
Chunked extraction	Extract small pieces across many turns	High — individual pieces may pass filters
Indirect extraction	Have 模型 reveal data through behavior changes	Very High — no explicit data in 輸出

Cross-Model Considerations

Techniques that work against one model may not directly transfer to others. 然而, 理解 the general principles allows adaptation:

安全訓練 methodology: Models trained with RLHF (GPT-4, Claude) have different 安全 characteristics than those using DPO (Llama, Mistral) or other methods. RLHF-trained models tend to refuse more broadly but may be more susceptible to multi-turn escalation.
Context window size: Models with larger context windows (Claude with 200K, Gemini with 1M+) may be more susceptible to 上下文視窗 manipulation where 對抗性 content is buried in large amounts of benign text.
Multimodal capabilities: Models that process images, audio, or other modalities introduce additional attack surfaces not present in text-only models.
工具使用實作: The 實作 details of 函式呼叫 vary significantly between providers. OpenAI uses a structured 函式呼叫 format, while Anthropic uses 工具使用 blocks. These differences affect 利用 techniques.

Operational Considerations

測試 Ethics and Boundaries

Professional 紅隊測試 operates within clear ethical and legal boundaries:

Authorization: Always obtain written 授權 before 測試. This should specify the scope, methods allowed, and any restrictions.
Scope limits: Stay within the authorized scope. If you discover a 漏洞 that leads outside the authorized perimeter, document it and report it without exploiting it.
Data handling: Handle any sensitive data discovered during 測試 according to the engagement agreement. Never retain sensitive data beyond what's needed for reporting.
Responsible disclosure: Follow responsible disclosure practices for any 漏洞 discovered, particularly if they affect systems beyond your 測試 scope.

Documenting Results

Professional documentation follows a structured format:

from dataclasses import dataclass, field
from datetime import datetime
from typing import Optional
 
@dataclass
class Finding:
    """Structure for documenting a 安全 finding."""
    id: str
    title: str
    severity: str  # Critical, High, Medium, Low, Informational
    category: str  # OWASP LLM Top 10 category
    description: str
    steps_to_reproduce: list[str]
    impact: str
    recommendation: str
    evidence: list[str] = field(default_factory=list)
    mitre_atlas: Optional[str] = None
    cvss_score: Optional[float] = None
    discovered_at: str = field(default_factory=lambda: datetime.now().isoformat())
 
    def to_report_section(self) -> str:
        """Generate a report section for this finding."""
        steps = "\n".join(f"   {i+1}. {s}" for i, s in enumerate(self.steps_to_reproduce))
        return f"""
### {self.id}: {self.title}
 
**Severity**: {self.severity}
**Category**: {self.category}
{f"**MITRE ATLAS**: {self.mitre_atlas}" if self.mitre_atlas else ""}
 
#### Description
{self.description}
 
#### Steps to Reproduce
{steps}
 
#### Impact
{self.impact}
 
#### Recommendation
{self.recommendation}
"""

This structured approach ensures that findings are actionable and that remediation teams have the information they need to address the 漏洞 effectively.

防禦-in-depth: No single defensive measure is sufficient. Layer multiple independent 防禦 so that failure of any single layer does not result in system compromise. 輸入 classification, 輸出 filtering, behavioral 監控, and architectural controls should all be present.
Assume breach: Design systems assuming that any individual component can be compromised. This mindset leads to better isolation, 監控, and incident response capabilities. When a 提示詞注入 succeeds, the blast radius should be minimized through architectural controls.
Least privilege: Grant models and 代理 only the minimum capabilities needed for their intended function. A customer service chatbot does not need file system access or code execution. Excessive capabilities magnify the impact of successful 利用.
Continuous 測試: AI 安全 is not a one-time 評估. Models change, 防禦 evolve, and new attack techniques are discovered regularly. 實作 continuous 安全測試 as part of the development and deployment lifecycle.
Secure by default: Default configurations should be secure. Require explicit opt-in for risky capabilities, use allowlists rather than denylists, and err on the side of restriction rather than permissiveness.

Integration with Organizational 安全

AI 安全 does not exist in isolation — it must integrate with the organization's broader 安全 program:

安全 Domain	AI-Specific Integration
Identity and Access	API key management, model access controls, user 認證 for AI features
Data Protection	訓練資料 classification, PII in prompts, data residency for model calls
Application 安全	AI feature threat modeling, 提示詞注入 in SAST/DAST, secure AI design patterns
Incident Response	AI-specific playbooks, model behavior 監控, 提示詞注入 forensics
Compliance	AI regulatory mapping (EU AI Act, NIST), AI audit trails, model documentation
Supply Chain	Model provenance, dependency 安全, adapter/weight integrity verification

class OrganizationalIntegration:
    """Framework for integrating AI 安全 with organizational 安全 programs."""
 
    def __init__(self, org_config: dict):
        self.config = org_config
        self.gaps = []
 
    def assess_maturity(self) -> dict:
        """評估 the organization's AI 安全 maturity."""
        domains = {
            "governance": self._check_governance(),
            "technical_controls": self._check_technical(),
            "監控": self._check_monitoring(),
            "incident_response": self._check_ir(),
            "訓練": self._check_training(),
        }
        overall = sum(d["score"] for d in domains.values()) / len(domains)
        return {"domains": domains, "overall_maturity": round(overall, 1)}
 
    def _check_governance(self) -> dict:
        has_policy = self.config.get("ai_security_policy", False)
        has_framework = self.config.get("risk_framework", False)
        score = (int(has_policy) + int(has_framework)) * 2.5
        return {"score": score, "max": 5.0}
 
    def _check_technical(self) -> dict:
        controls = ["input_classification", "output_filtering", "rate_limiting", "sandboxing"]
        active = sum(1 for c in controls if self.config.get(c, False))
        return {"score": active * 1.25, "max": 5.0}
 
    def _check_monitoring(self) -> dict:
        has_monitoring = self.config.get("ai_monitoring", False)
        has_alerting = self.config.get("ai_alerting", False)
        score = (int(has_monitoring) + int(has_alerting)) * 2.5
        return {"score": score, "max": 5.0}
 
    def _check_ir(self) -> dict:
        has_playbook = self.config.get("ai_ir_playbook", False)
        return {"score": 5.0 if has_playbook else 0.0, "max": 5.0}
 
    def _check_training(self) -> dict:
        has_training = self.config.get("ai_security_training", False)
        return {"score": 5.0 if has_training else 0.0, "max": 5.0}

Future Directions

Several research and industry trends will shape the evolution of this field:

Formal methods for AI 安全: Development of mathematical frameworks that can provide bounded guarantees about model behavior under 對抗性 conditions
Automated 紅隊演練 at scale: Continued improvement of automated 測試 tools that can discover novel 漏洞 without human guidance
AI-assisted 防禦: Using AI systems to detect and respond to attacks on other AI systems, creating a dynamic attack-防禦 ecosystem
Standardized 評估: Growing adoption of standardized benchmarks (HarmBench, JailbreakBench) that enable consistent measurement of progress
Regulatory harmonization: Convergence of AI regulatory frameworks across jurisdictions, providing clearer requirements for organizations

Sandboxing and Permission 模型s for 工具-Using 代理s

Related articles

Sandboxing and Permission 模型s for 工具-Using 代理s

Related articles