Strike48 Labs Strike48 Labs

Getting Started

Accessing StrikeKit

StrikeKit is accessed through Strike48 Studio:

  1. Navigate to your Strike48 Studio instance
  2. Select the StrikeKit application
  3. Log in with your credentials
  4. StrikeKit interface loads in your browser

Note: StrikeKit runs as part of the Strike48 platform. Installation instructions are available for Strike-Labs deployments only.

Creating Your First Engagement

  1. Navigate to Headquarters → Engagements
  2. Click Create Engagement
  3. Fill in engagement details:
    • Name: Project identifier
    • Client: Client organization name
    • Type: Internal/External/Web App/Social Engineering/Physical
    • Start Date: Engagement start date
    • End Date: Engagement end date
    • Scope: IP ranges, domains, or systems in scope
    • Rules of Engagement: Constraints and limitations
  4. Click Save
  5. Select the engagement from the dropdown at the top of the sidebar

Once an engagement is active, engagement-specific views will become available.

Interface Overview

StrikeKit's interface is organized into logical sections that flow from top to bottom:

  • Headquarters: Command center (Assistant, Dashboard, Engagements, Templates)
  • Mission: Planning and execution (Planning, Execution, Objectives, Pivot Chains, Checklists)
  • Intelligence: Data collection (Targets, Domains, Vulnerabilities, OSINT)
  • Analysis: Findings and evidence (Credentials, Evidence, Findings, Network Topology)
  • Tracking: Progress monitoring (Kill Chain, Timeline, Audit Log, Blockers)
  • Reporting: Deliverables (Notes, MITRE ATT&CK, Reports)
  • Toolkit: Operational tools (Reconnaissance, C2)
  • System: Configuration (Diagnostics, Settings)

For a detailed walkthrough of the interface, see Interface Overview.

See the Workflow Guide for the recommended approach to running engagements with StrikeKit.

Next Steps

Now that you have StrikeKit installed and your first engagement created:

  1. Interface Overview - Learn the complete interface
  2. Workflow Guide - Follow the recommended engagement workflow
  3. Create Targets - Add systems to test
  4. Set Up C2 - Configure command and control
  5. Document Findings - Record discovered vulnerabilities

Request Access

StrikeKit requires an entitlement to use. If you'd like access, join our Discord server and let us know — we'll get you set up.

Related Documentation: