implementing-cloud-workload-protection

Implements runtime security monitoring for EC2 and GCE instances using boto3 and SSM.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill implementing-cloud-workload-protection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementing-cloud-workload-protection
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/cloud-security/implementing-cloud-workload-protection
Command: npx skills add https://github.com/xalgord/xalgorix --skill implementing-cloud-workload-protection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires boto3.

What problem does it solve?

Cloud compute workloads are frequent targets for cryptominers, reverse shells, and unauthorized binaries, but detecting these runtime threats requires continuous process, network, and file integrity monitoring that is tedious to build manually.

Core Features & Use Cases

  • Process Monitoring: Runs remote commands via AWS Systems Manager to detect cryptominers (xmrig, minerd) and reverse shells on EC2 instances.
  • Network & File Integrity Auditing: Checks outbound connections for C2 callbacks and compares binary hashes against known-good baselines.
  • Anomaly Detection Guidance: Covers CPU spike detection, baseline capture, and common misconfigurations like unmanaged SSM agents and unchecked command results.
  • Use Case: A security engineer needs to verify that a fleet of EC2 instances has not been compromised by cryptomining malware; this Skill provides the boto3/SSM commands and verification steps to scan and confirm findings.

Quick Start

Ask the AI to write a boto3 script that uses AWS Systems Manager to scan my EC2 instances for cryptomining processes and suspicious outbound connections.

Frequently Asked Questions about implementing-cloud-workload-protection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect cryptominers on EC2 instances with boto3?

Use boto3's SSM client to run send_command with the AWS-RunShellScript document, executing commands like ps aux piped to grep for xmrig, minerd, or cryptonight signatures. Retrieve results with list-command-invocations since send_command returns immediately.

How to check for suspicious outbound connections on cloud instances?

Run ss -tlnp or ss -tnp through SSM send_command to list established connections with owning processes. Review the output for unexpected remote endpoints that may indicate C2 callbacks.

Why does SSM send_command not run on my EC2 instance?

The instance must be managed by Systems Manager, which requires the SSM agent installed, an IAM role with AmazonSSMManagedInstanceCore, and network access via an SSM VPC endpoint or NAT. Verify status with aws ssm describe-instance-information.

What are the limitations of grep-based malware detection?

Signature matching on names like xmrig or minerd misses renamed or repacked miners and reverse shells. Combine it with binary hash comparison against a known-good baseline and outbound connection review for reliable detection.

Does this workload protection approach work without a baseline?

No, anomaly detection without a recorded normal process, network, and CPU profile produces only noise. Capture a baseline per instance role first, then compare runtime observations against it.