Skip to main content
Glama

apply_defender_profile

Enhance Ludus configurations with security monitoring, logging, and detection capabilities for blue team training, SOC practice, and threat hunting exercises.

Instructions

Apply defender profile to add monitoring and detection capabilities for blue team training.

This tool enhances an existing Ludus configuration with comprehensive security monitoring, logging, and detection capabilities. Perfect for:

  • Blue team training and SOC practice

  • SIEM deployment and configuration

  • Threat hunting exercises

  • Purple team defensive exercises

  • Incident detection and response training

Args: config: The Ludus range configuration to enhance (dict with 'ludus' key) monitoring_level: Level of monitoring to deploy - "basic": SIEM agent + event forwarding - "comprehensive": + Sysmon/Auditd + PowerShell logging - "advanced": + EDR, process monitoring, FIM, network monitoring siem_type: SIEM platform to deploy - "wazuh": Wazuh (open source SIEM/XDR) - "splunk": Splunk Enterprise - "elastic": Elastic Stack (ELK) detection_focus: Optional list of specific attack types to focus detection on (e.g., ["kerberos_attacks", "lateral_movement", "credential_access"])

Returns: Dictionary containing: - status: "success" - profile_type: "defender" - monitoring_level: The applied monitoring level - siem_type: The SIEM platform used - modified_config: Enhanced Ludus configuration - monitoring_enhancements: List of added monitoring capabilities - enhancements_count: Total number of enhancements - siem_added: Whether SIEM server was added - detection_rules: List of detection rules configured - affected_vms: List of VMs that were enhanced - documentation: Implementation and usage documentation - next_steps: What to do after deployment

Examples: # Add comprehensive Wazuh monitoring to all VMs result = await apply_defender_profile( config=my_range_config, monitoring_level="comprehensive", siem_type="wazuh" )

# Add advanced monitoring with Splunk
result = await apply_defender_profile(
    config=my_range_config,
    monitoring_level="advanced",
    siem_type="splunk"
)

# Focus detection on Kerberos attacks and lateral movement
result = await apply_defender_profile(
    config=my_range_config,
    monitoring_level="comprehensive",
    siem_type="wazuh",
    detection_focus=["kerberos_attacks", "lateral_movement"]
)

Monitoring Capabilities: Windows Monitoring: - SIEM agent (Wazuh/Splunk/Elastic) - Event log forwarding - Sysmon (process, network, file monitoring) - PowerShell script block logging - EDR capabilities (advanced level) - Process monitoring (advanced level) - File integrity monitoring (advanced level)

Linux Monitoring:
    - SIEM agent (Wazuh/Splunk/Elastic)
    - Syslog forwarding
    - Auditd (system call auditing)
    - OSQuery (endpoint visibility)
    - EDR capabilities (advanced level)
    - Process monitoring (advanced level)
    - File integrity monitoring (advanced level)

Network Monitoring:
    - NetFlow collection
    - Packet capture
    - Zeek network security monitor (advanced level)
    - Suricata IDS/IPS (advanced level)

Detection Rules: - Kerberoasting detection (Event ID 4769) - Lateral movement detection (PsExec, WMI) - Credential dumping (LSASS access, Mimikatz) - PowerShell obfuscation - Suspicious process execution - And more based on detection_focus

Notes: - SIEM server will be automatically added if not present - All VMs will have monitoring agents installed - Detection rules are pre-configured but customizable - Dashboard and alerting must be configured post-deployment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
configYes
monitoring_levelNocomprehensive
siem_typeNowazuh
detection_focusNo
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and does well by disclosing key behavioral traits: it describes what gets enhanced (monitoring, logging, detection), notes that 'SIEM server will be automatically added if not present', and mentions post-deployment steps like dashboard configuration. However, it lacks details on permissions, rate limits, or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections like 'Args', 'Returns', 'Examples', and 'Notes', but it is overly verbose with extensive lists (e.g., 'Monitoring Capabilities', 'Detection Rules') that could be condensed. Some sentences, like the bullet points, do not earn their place for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 4 parameters, no annotations, and no output schema, the description is mostly complete: it explains inputs, outputs, examples, and behavioral notes. However, it lacks explicit error conditions, authentication requirements, or performance implications, leaving minor gaps in context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Given 0% schema description coverage, the description fully compensates by detailing all 4 parameters: 'config' is explained as a Ludus range configuration, 'monitoring_level' with enum values and capabilities, 'siem_type' with platform options, and 'detection_focus' with examples. This adds significant meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('apply', 'enhance') and resources ('defender profile', 'Ludus configuration'), and distinguishes it from siblings like 'apply_adversary_profile' by focusing on defensive monitoring capabilities for blue team training rather than offensive actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool (e.g., 'blue team training', 'SOC practice', 'threat hunting exercises'), but does not explicitly state when not to use it or name specific alternatives among siblings, such as 'apply_adversary_profile' for offensive scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tjnull/Ludus-FastMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server