Getting Started with blackLen

Welcome to blackLen, a unified offensive security command platform engineered for penetration testers, red teams, and security auditors.

---

The Core Onboarding Flow

1. Create Account & Log In: Access your personal workspace environment.
2. Establish Organization: Create a shared workspace for your security consultancy, internal team, or research unit.
3. Invite Team Members: Add colleagues and assign organization governance roles.
4. Create an Engagement Project: Define a discrete assessment boundary.
5. Scope Target Assets: Add domains, CIDRs, web applications, and repositories.
6. Execute Interactive Checklists: Run verification steps, record findings, and link tools.

---

1. Workspace Identity & Contexts

blackLen operates across two primary operational contexts:

1. User Context (Personal Workspace): Your personal research hub for maintaining private exploit scripts, exploratory payload lists, and personal checklists.
2. Organization Context (Team Workspace): A shared workspace where your security consultancy, internal red team, or audit firm collaborates on client engagements.

Creating Your First Organization:

1. Log in to the blackLen workspace.
2. Navigate to the top workspace selector and click + New Organization.
3. Provide your Organization Name and Workspace Slug (e.g., acme-security).
4. As the creator, you are automatically assigned the Owner role with full administrative authority.

---

2. Inviting Your Team

Invite security engineers, external auditors, and client observers to your organization with granular roles:

---

3. Creating an Engagement Project

A Project represents a discrete security engagement, penetration test, or red team campaign.

Setup Steps:

1. Navigate to Projects → Click + Create Project.
2. Enter the Project Title (e.g., Q3 Web Application Penetration Test), Client Name, and Engagement Dates.
3. Set the project Status (Pending, Active, On Hold, Completed, Cancelled).
4. Assign project members with specific execution roles:
   • Admin: Lead penetration tester managing the engagement.
   • Editor: Senior tester managing scope and checklist structure.
   • Tester: Active tester executing audit steps and recording findings.
   • Auditor: Compliance tester with "Tick-Mark Only" execution rights.
   • Viewer: Client or stakeholder with read-only progress visibility.

---

4. Defining Attack Surface Scope

Define the engagement perimeter before executing tests:

• Domains & Wildcards: example.com, *.example.com
• IP Addresses & CIDR Ranges: 192.168.1.50, 10.0.0.0/24
• Web Applications & APIs: https://app.example.com, https://api.example.com/v1/
• Repositories & Mobile Apps: Git repository URLs, Play Store IDs, iOS App Store IDs.

You can add assets manually or import scoped targets simultaneously using the built-in CSV Bulk Ingestion tool.

---

5. Launching an Interactive Checklist

1. In your project, go to Checklists → Click + Add Checklist.
2. Select an existing Checklist Template or create a custom checklist tailored to the target scope.
3. Open the checklist to review interactive verification steps.
4. As you test, toggle item states (Pass, Fail, In Progress, Blocked, N/A, Skipped) and document findings in the Evidence and Notes fields.