Jump to Content
Guardicore Infection Monkey
Guide
TrainingSupportCommunityGuardicore Infection Monkey
TrainingSupportCommunity
Guide

Welcome

  • Guardicore Infection Monkey documentation hub

Setup

  • Setting up Infection Monkey
  • Windows
  • Docker
  • Linux
  • AWS
  • Azure
  • Accounts and security

Usage

  • Usage
  • Getting started
  • Scenarios
  • Ransomware simulation
  • Custom
    • Zero Trust assessment
    • MITRE ATT&CK assessment
    • Network breach
    • Network segmentation
    • Credentials leak
    • Other
  • Configuration
    • Credentials
    • Network
  • Integrations
    • ScoutSuite
    • Running the Monkey on AWS EC2 instances
    • AWS Security Hub integration
  • Verify integrity- checksums

Contribute

  • Securing networks together
  • Swimm tutorials
  • Development setup
  • Adding exploits
  • Adding System Info Collectors
  • Adding post-breach actions
  • Adding Zero Trust tests

Reference

  • Reference
  • Data directory
  • MITRE ATT&CK
  • Operating Systems
  • Scanners
  • Exploiters
    • Log4Shell
    • PowerShell
    • Zerologon
    • Drupal
    • WMIexec
    • MS08-067
    • WebLogic
    • VSFTPD
    • Struts2
    • SSHexec
    • SMBexec
    • Sambacry
    • MsSQL
    • Hadoop
    • ElasticGroovy
    • ShellShock
  • Server configuration

Reports

  • Infection Monkey reports
  • Security report
  • Zero Trust report
  • MITRE ATT&CK report
  • Ransomware report

FAQs

  • Frequently asked questions

Network

Suggest Edits

Here you can control multiple important settings, such as:

  • Network propagation depth - How many hops from the base machine will the Infection Monkey spread?
  • Local network scan - Should the Infection Monkey attempt to attack any machine in its subnet?
  • Scanner IP/subnet list - Which specific IP ranges should the Infection Monkey should try to attack?

Updated 5 months ago