Category: Uncategorized

  • The Complete Guide to Open-Source AI/LLM Security Tools: From Model Testing to Agentic System Analysis

    As AI and Large Language Models (LLMs) become increasingly integrated into critical applications and complex agentic workflows, the need for robust security tools has never been greater. This comprehensive guide examines the current landscape of open-source AI security tools, organizing them by the level and aspect of the AI ecosystem they address.

    Understanding the AI Security Ecosystem

    The AI/LLM security landscape operates at different levels, from individual model testing to complete system architecture analysis. Understanding these levels is crucial for selecting appropriate tools for specific security needs and building comprehensive defense strategies.


    1. Model-Level Testing

    Testing core LLM capabilities, vulnerabilities, and behaviors

    Individual Model Security

    Garak (NVIDIA)

    PyRIT (Microsoft Azure)

    • Purpose: Python Risk Identification Tool for generative AI
    • Key Features: LLM-based evaluators with explainability, customizable attacks, multi-step jailbreaks
    • Supports: Framework-agnostic approach for individual LLM testing
    • Links: GitHub: https://github.com/Azure/PyRIT

    Adversarial Robustness Toolbox (ART)

    Purple Llama/CyberSecEval (Meta)

    • Purpose: Cybersecurity evaluation benchmark for LLMs
    • Key Features: Insecure code generation detection, malicious request compliance testing
    • Focus: Cybersecurity framework alignment and comprehensive benchmarking
    • Links: GitHub: https://github.com/meta-llama/PurpleLlama

    2. Application-Level Security

    How LLMs are integrated and used within applications

    Application Integration Testing

    promptfoo

    Giskard

    • Purpose: ML model testing and validation platform
    • Key Features: Multi-language support, structured attack customization, LLM guardrails interface
    • Focus: Broader ML application focus with LLM capabilities

    3. System-Level Analysis

    Multi-agent systems, workflows, and architectural analysis

    Agentic Workflow Analysis

    Agentic Radar (SplxAI)

    agentic_security

    • Purpose: Vulnerability scanner specifically for Agent Workflows and LLMs
    • Key Features: Multimodal attacks, multi-step jailbreaks, RL-based adaptive attacks
    • Focus: API integration and stress testing for agentic systems
    • Links: GitHub: https://github.com/msoedov/agentic_security

    4. Runtime Protection & Monitoring

    Real-time guardrails, monitoring, and operational security

    Input/Output Guardrails

    Guardrails AI

    LlamaFirewall (Meta)

    • Purpose: Real-time guardrails for language model agents
    • Key Features: PromptGuard 2, CodeShield, AlignmentCheck modules
    • Focus: Production deployment guardrails and real-time protection
    • Links: Analysis: https://threatmodel.co/blog/llamafirewall-ai

    Invariant Guardrails


    Tool Comparison Matrix

    ToolLevelFocusApproachAgentic Support
    Agentic RadarSystemWorkflow AnalysisStatic + DynamicFull
    GarakModelVulnerability ScanningDynamicLimited
    PyRITModelRed TeamingDynamicLimited
    Guardrails AIRuntimeInput/Output ProtectionRuntimePartial
    ARTModelAdversarial MLStatic + DynamicNone
    promptfooApplicationTesting PlatformDynamicPartial
    LlamaFirewallRuntimeReal-time ProtectionRuntimePartial
    agentic_securitySystemAgent VulnerabilitiesDynamicFull

    Integration Recommendations

    Complementary Tool Stacks

    Development Stack

    • Agentic Radar (static analysis)
    • promptfoo (dynamic testing)
    • Guardrails AI (runtime protection)

    Research Stack

    • Garak (model testing)
    • PyRIT (advanced red teaming)
    • ART (adversarial robustness)

    Production Stack

    • LlamaFirewall (runtime guardrails)
    • Invariant Guardrails (system-level rules)
    • Purple Llama (compliance)

    Key Insights

    1. Agentic Radar is unique in providing comprehensive system-level analysis of agentic workflows with visualization capabilities.
    2. Most tools focus on individual LLM testing rather than complete system architecture analysis.
    3. Runtime protection tools (Guardrails AI, LlamaFirewall) complement static analysis tools for comprehensive security.
    4. The ecosystem is evolving rapidly with new tools emerging to address different aspects of AI security.
    5. No single tool addresses all security concerns – a layered approach using multiple tools is recommended for comprehensive coverage.

    Conclusion

    The AI/LLM security landscape is rapidly evolving, with tools addressing different layers of the technology stack. While most focus on individual model testing or runtime protection, there’s a growing recognition of the need for system-level analysis of complex agentic workflows.

    Organizations building AI systems should adopt a layered security approach, combining tools from different levels to achieve comprehensive coverage. As agentic AI systems become more prevalent, tools like Agentic Radar that provide architectural transparency and workflow analysis will become increasingly critical for maintaining security and compliance.

    The key is to understand where each tool fits in your security strategy and how they can work together to create a robust defense against the evolving landscape of AI security threats.


    References

    • Comparative Analysis Paper: https://arxiv.org/abs/2410.16527
    • OWASP LLM Top 10: Referenced across multiple tools for vulnerability classification
    • Various vendor documentation and blog posts provide additional context and usage examples

    Academic Research Foundations

    The tools and frameworks discussed above are grounded in extensive academic research. Here are the key papers that form the theoretical foundation of AI security tools and practices.

    Foundational AI Security Frameworks

    Core Security Framework Papers

    • PyRIT: A Framework for Security Risk Identification and Red Teaming in Generative AI Systems (2024)
      https://arxiv.org/abs/2410.02828
      Microsoft’s comprehensive framework that forms the basis for modern AI red teaming practices.
    • garak: A Framework for Security Probing Large Language Models (2024)
      https://arxiv.org/abs/2406.11036
      NVIDIA’s academic foundation for systematic LLM vulnerability assessment.
    • Lessons From Red Teaming 100 Generative AI Products (2025)
      https://arxiv.org/abs/2501.07238
      Microsoft’s practical insights from extensive real-world AI red teaming operations.
    • Red-Teaming for Generative AI: Silver Bullet or Security Theater? (2024)
      https://arxiv.org/abs/2401.15897
      Critical academic analysis of AI red teaming practices and their limitations.

    Agentic AI Security Research

    The most relevant research for tools like Agentic Radar that focus on multi-agent and agentic system security.

    Multi-Agent System Security

    • Securing Agentic AI: A Comprehensive Threat Model and Mitigation Framework (2024)
      https://arxiv.org/abs/2504.19956
      Most comprehensive academic threat model specifically for agentic AI systems.
    • Open Challenges in Multi-Agent Security: Towards Secure Systems of Interacting AI Agents (2024)
      https://arxiv.org/abs/2505.02077
      Academic analysis of security vulnerabilities in interacting multi-agent systems.
    • Security of AI Agents (2024)
      https://arxiv.org/abs/2406.08689
      Systematic analysis of AI agent vulnerabilities and defense mechanisms.
    • Position: Towards a Responsible LLM-empowered Multi-Agent Systems (2025)
      https://arxiv.org/abs/2502.01714
      Framework for responsible development of multi-agent LLM systems.

    AI Security Evaluation Research

    • Insights and Current Gaps in Open-Source LLM Vulnerability Scanners: A Comparative Analysis (2024)
      https://arxiv.org/abs/2410.16527
      Direct academic comparison of Garak, Giskard, PyRIT, and CyberSecEval tools.
    • AI Benchmarks and Datasets for LLM Evaluation (2024)
      https://arxiv.org/abs/2412.01020
      Comprehensive framework for AI system evaluation including security aspects.
    • Adversarial Testing in LLMs: Insights into Decision-Making Vulnerabilities (2025)
      https://arxiv.org/abs/2505.13195
      Framework for stress-testing LLM decision-making processes under adversarial conditions.

    Emerging Trends in AI Security

    Based on current research and development patterns, several key trends are shaping the future of AI security tools and practices.

    1. Agentic-Specific Security Focus

    The field is rapidly recognizing that agentic AI systems require fundamentally different security approaches than traditional LLMs. We’re seeing the emergence of specialized frameworks like Agentic Radar and dedicated research initiatives such as the OWASP Agentic Security Initiative and CSA’s MAESTRO framework.

    2. Industry Standardization Efforts

    Major organizations are developing standardized approaches to AI security assessment. OWASP has expanded beyond their LLM Top 10 to address agentic systems specifically, while the Cloud Security Alliance (CSA) has introduced the MAESTRO threat modeling framework.

    3. Automated Red Teaming Evolution

    Tools like PyRIT and Garak are pioneering automated approaches to AI red teaming, but the field is evolving toward more sophisticated automation including AI-vs-AI testing scenarios and reinforcement learning-based attack generation.

    4. Integration of Static and Dynamic Analysis

    Modern AI security tools are moving beyond single-mode analysis. Tools like Agentic Radar combine static workflow analysis with dynamic runtime testing, providing comprehensive coverage of potential vulnerabilities.

    5. Real-Time Monitoring and Guardrails

    The field is shifting from purely testing-focused tools to integrated monitoring and protection systems that provide continuous runtime protection rather than just vulnerability assessment.

    6. Multi-Modal Security Assessment

    As AI systems increasingly work with text, images, audio, and video, security tools are expanding to cover multi-modal attack vectors and complex attacks that combine multiple input types.

    7. Framework-Specific Security Tools

    Rather than generic approaches, we’re seeing the development of tools tailored to specific AI development frameworks that can understand the specific architectural patterns and vulnerabilities of different development approaches.

    8. Community-Driven Security Intelligence

    Open-source security tools are increasingly leveraging community contributions for vulnerability signatures, attack patterns, and defense strategies.

    9. Regulatory Compliance Integration

    With the emergence of AI-specific regulations like the EU AI Act, security tools are being designed with compliance assessment built-in.

    10. Cross-System Vulnerability Analysis

    As AI systems become more interconnected, security tools are evolving to analyze vulnerabilities that span multiple systems, platforms, and organizations.

  • How to Set Up WordPress MCP for AI Integration on AWS Lightsail Bitnami

    Overview

    This guide will help you set up WordPress MCP (Model Context Protocol) functionality on your AWS Lightsail Bitnami WordPress installation, enabling AI assistants like Claude to interact directly with your WordPress site.

    Prerequisites

    • AWS Lightsail Bitnami WordPress instance
    • SSH access to your server
    • Node.js 22+ on your local machine
    • Basic familiarity with WordPress admin and command line

    Part 1: Install WordPress Plugins on Your Server

    Step 1: Access Your Server

    # SSH into your Lightsail instance
    ssh bitnami@YOUR_SERVER_IP

    Step 2: Install WordPress Feature API Plugin

    # Navigate to WordPress plugins directory
    cd /opt/bitnami/wordpress/wp-content/plugins/
    
    # Clone the wp-feature-api repository
    sudo git clone https://github.com/Automattic/wp-feature-api.git
    
    # Change ownership to the web server user
    sudo chown -R bitnami:daemon wp-feature-api/
    
    # Navigate into the plugin directory
    cd wp-feature-api/
    
    # Install dependencies and build
    sudo npm run setup
    sudo npm run build

    Step 3: Install WordPress MCP Plugin

    # Navigate back to plugins directory
    cd /opt/bitnami/wordpress/wp-content/plugins/
    
    # Clone the wordpress-mcp repository
    sudo git clone https://github.com/Automattic/wordpress-mcp.git
    
    # Change ownership
    sudo chown -R bitnami:daemon wordpress-mcp/
    
    # Navigate into the plugin directory
    cd wordpress-mcp/
    
    # Install PHP dependencies
    sudo composer install --no-dev
    
    # Install npm dependencies and build
    sudo npm install
    sudo npm run build

    Part 2: Configure WordPress

    Step 4: Activate Plugins

    • Log into your WordPress admin dashboard
    • Navigate to PluginsInstalled Plugins
    • Activate WordPress Feature API
    • Activate WordPress MCP

    Step 5: Configure MCP Settings

    • Go to SettingsMCP in your WordPress admin
    • Enable MCP functionality
    • Configure which features/tools you want to expose
    • Save settings

    Step 6: Create Application Password

    • Go to UsersYour Profile
    • Scroll down to Application Passwords
    • Enter a name like “MCP Client”
    • Click Add New Application Password
    • IMPORTANT: Copy the generated password immediately – you won’t see it again!

    Part 3: Configure Local MCP Client

    Step 7: Configure Claude Desktop

    Create or edit your Claude Desktop configuration file:

    macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    Windows: %APPDATA%\Claude\claude_desktop_config.json

    {
      "mcpServers": {
        "wordpress-mcp": {
          "command": "npx",
          "args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
          "env": {
            "WP_API_URL": "https://YOUR_LIGHTSAIL_DOMAIN.com",
            "WP_API_USERNAME": "your-username",
            "WP_API_PASSWORD": "your-application-password"
          }
        }
      }
    }

    Replace:

    • YOUR_LIGHTSAIL_DOMAIN.com with your actual domain
    • your-username with your WordPress username
    • your-application-password with the application password you generated

    Step 8: Configure Cursor (Alternative)

    Create ~/.cursor/mcp.json:

    {
      "mcpServers": {
        "wordpress-mcp": {
          "command": "npx",
          "args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
          "env": {
            "WP_API_URL": "https://YOUR_LIGHTSAIL_DOMAIN.com",
            "WP_API_USERNAME": "your-username",
            "WP_API_PASSWORD": "your-application-password"
          }
        }
      }
    }

    Critical Configuration Notes

    ⚠️ Username Requirements

    Make sure you use the correct username! The most common authentication issues are:

    • Try your exact WordPress username first (the one you use to log in)
    • If that doesn’t work, try your email address instead
    • The username is case-sensitive
    • Make sure the user has Administrator privileges

    🔑 Application Password Spaces

    REMOVE ALL SPACES from the application password!

    WordPress displays application passwords with spaces for readability, but you must remove them:

    • WordPress shows: AbCd EfGh IjKl MnOp
    • You must use: AbCdEfGhIjKlMnOp

    This is the #1 cause of authentication failures!

    Testing Your Setup

    Step 9: Test the Connection

    • Restart Claude Desktop or Cursor
    • In a new chat, try asking: “Can you tell me about my WordPress site?”
    • If configured correctly, Claude should be able to access your site information

    Step 10: Available Commands

    Once connected, you can ask Claude to:

    • List posts, pages, users
    • Create and edit content
    • Manage media files
    • Analyze site settings
    • And much more!

    Troubleshooting

    Common Issues

    • Connection Failed: Check your API URL, username, and application password
    • Permission Denied: Ensure the WordPress user has Administrator permissions
    • SSL Errors: Make sure your site has a valid SSL certificate
    • Plugin Not Working: Verify plugins are activated and built correctly

    Debug Steps

    • Check WordPress error logs: /opt/bitnami/wordpress/wp-content/debug.log
    • Test API access manually:
    curl -u username:app_password https://yoursite.com/wp-json/wp/v2/posts
    • Check MCP logs if LOG_FILE is configured in your client setup

    Important Notes

    • Bitnami Specifics: File paths use /opt/bitnami/wordpress/ instead of standard WordPress paths
    • Permissions: Always use sudo for file operations and set proper ownership
    • Updates: When updating plugins, you may need to rebuild them
    • Backups: Always backup your site before making changes

    Support Resources

    Security Configuration (Critical Step)

    ⚠️ Important: When you install plugins using git clone, you expose sensitive files that should never be accessible via web browser. This is a critical security risk that must be addressed.

    Why Security Configuration is Required

    When you run git clone to install WordPress MCP plugins, you’re downloading the entire development repository, which includes:

    • .git/ directory – Contains complete repository history, potentially including sensitive information
    • Configuration filescomposer.json, package.json, webpack.config.js reveal your tech stack and dependencies
    • Development files – Build scripts, documentation, and temporary files
    • Dependenciesnode_modules/, vendor/ directories (if present)
    • Environment files – Any .env files or configuration that might contain secrets

    These files are meant for development, not production, and can reveal sensitive information about your server setup to attackers.

    Security Risk Assessment

    High Risk Files:

    • .git/Entire repository history including potentially sensitive commits
    • composer.json/package.jsonDependency information that reveals software versions
    • Build configuration files – Technical details about your setup

    What Attackers Can Learn:

    • Your development workflow and tools
    • Software versions you’re running (for exploit targeting)
    • Repository history and previous configurations
    • Internal file structures and organization

    Security Implementation Options

    Choose one of these approaches:

    Option 1: Remove Sensitive Files (Recommended – Simplest)

    After plugin installation and building, clean up sensitive files:

    # Navigate to WordPress MCP plugin
    cd /opt/bitnami/wordpress/wp-content/plugins/wordpress-mcp/
    
    # Remove git history and development files
    sudo rm -rf .git/
    sudo rm -f composer.json composer.lock package.json package-lock.json
    sudo rm -f webpack.config.js tsconfig.json .eslintrc.js
    sudo rm -f *.md README.md CONTRIBUTING.md
    sudo rm -rf node_modules/ tests/ docs/
    
    # Repeat for WordPress Feature API plugin
    cd /opt/bitnami/wordpress/wp-content/plugins/wp-feature-api/
    
    sudo rm -rf .git/
    sudo rm -f composer.json composer.lock package.json package-lock.json
    sudo rm -f webpack.config.js tsconfig.json .eslintrc.js
    sudo rm -f *.md README.md CONTRIBUTING.md
    sudo rm -rf node_modules/ tests/ docs/
    
    # Set proper ownership
    sudo chown -R bitnami:daemon /opt/bitnami/wordpress/wp-content/plugins/
    

    Option 2: Apache Configuration Rules (Advanced)

    Add security rules to your Apache configuration:

    # Add security rules to Apache config
    sudo tee -a /opt/bitnami/apache/conf/httpd.conf << 'EOF'
    
    # WordPress Plugin Security Rules
    <DirectoryMatch "\.git">
        Require all denied
    </DirectoryMatch>
    
    <FilesMatch "\.(json|lock|md|yml|yaml|log|tmp)$">
        Require all denied
    </FilesMatch>
    
    <DirectoryMatch "node_modules">
        Require all denied
    </DirectoryMatch>
    
    <DirectoryMatch "(^|/)vendor/">
        Require all denied
    </DirectoryMatch>
    EOF
    

    Test and restart Apache:

    # Test configuration syntax
    sudo /opt/bitnami/apache/bin/httpd -t
    
    # If syntax is OK, restart services
    sudo /opt/bitnami/ctlscript.sh restart
    

    ⚠️ Note: If you get “Service Unavailable” errors after restart, the configuration may be too restrictive. Remove the added rules and use Option 1 instead.

    Security Verification

    After implementing security measures, test that sensitive files are properly blocked:

    # These commands should return "403 Forbidden" or "404 Not Found"
    # Replace your-domain.com with your actual domain
    
    curl -I https://your-domain.com/wp-content/plugins/wordpress-mcp/.git/
    curl -I https://your-domain.com/wp-content/plugins/wordpress-mcp/composer.json
    curl -I https://your-domain.com/wp-content/plugins/wordpress-mcp/package.json
    curl -I https://your-domain.com/wp-content/plugins/wp-feature-api/.git/
    

    ✅ Secure Response: HTTP/1.1 403 Forbidden or HTTP/1.1 404 Not Found
    ❌ Insecure Response: Any response that shows actual file content

    Best Practices for Future Updates

    When updating plugins:

    1. If using Option 1 (file removal):
      • Pull updates: git pull origin main
      • Rebuild: npm run build
      • Clean sensitive files again (repeat removal commands)
    2. If using Option 2 (Apache rules):
      • Updates are automatically protected
      • No additional cleanup needed

    For production deployments, consider:

    • Using official plugin releases instead of git clone
    • Implementing automated deployment scripts that clean sensitive files
    • Regular security audits of plugin directories

    Why This Matters

    Without proper security:

    • Attackers can access your entire development history
    • Technical details about your setup are exposed
    • Dependency information reveals potential vulnerabilities
    • Your site appears unprofessional and insecure

    With proper security:

    • Only necessary production files are accessible
    • Your technical stack remains private
    • Site appears professionally configured
    • Reduced attack surface for potential threats

    This security step is mandatory when using git clone for plugin installation and should never be skipped in production environments.