Lens Platform Documentation
Comprehensive guide for Crownstone consultants conducting cybersecurity assessments
Platform Overview
The Lens Assessment Platform is Crownstone's proprietary cybersecurity assessment tool implementing the Cybersecurist Lens™ framework. It enables consultants to systematically identify systemic security risks that traditional tools miss.
Full Engagement Workflow
Quick Start Guide
Get started with a new assessment in minutes by following these steps:
-
Create the Client RecordGo to Dashboard > Clients tab and click "New Client". Enter company name, industry, and primary contact information.
-
Create a New AssessmentFrom the Dashboard, click "New Assessment". Select the client, set assessment type, and define scope parameters.
-
Configure API IntegrationsIf the client uses Snyk or Wiz, add their API credentials in Assessment Settings > Connectors to pull findings automatically.
-
Import or Add FindingsImport scan results from security tools or manually add findings discovered during interviews and documentation review.
-
Review and Map to Lens QuestionsReview each finding, accept/modify/reject, and map to the appropriate Lens question (Q1-Q5) to enable systemic analysis.
-
Generate RecommendationsUse the AI recommendation generator to create actionable guidance for each accepted finding.
-
Create DeliverablesGenerate the assessment report, executive briefing, and remediation roadmap from the assessment page.
Client Intake Process
The client intake process captures essential information needed to scope and conduct the assessment effectively.
Required Client Information
| Field | Description | Why It Matters |
|---|---|---|
| Company Name | Legal entity name | Report headers, compliance documentation |
| Industry | Primary business sector | Industry-specific compliance requirements, threat landscape |
| Organization Size | Employee count bracket | Scale of recommendations, resource expectations |
| Security Maturity | Current maturity level (1-5) | Calibrates recommendation complexity |
| Primary Contact | Main stakeholder for engagement | Communication, approvals, scheduling |
| Technical Contact | IT/Security team point person | Technical questions, API access, scan coordination |
Using the Intake Form
Navigate to intake.html and share the link with the client. The form captures:
- Company demographics and industry classification
- Contact information (name, email, phone, role)
- Assessment trigger (compliance mandate, breach response, board requirement, etc.)
- Current security maturity self-assessment
- Budget range and timeline preference
- Top security concerns and priorities
Pipeline Integration
When a prospect submits the intake form:
-
Lead Created AutomaticallyA new lead is created in the Sales Pipeline with all intake data, including trigger, maturity, budget, and concerns.
-
Package RecommendedThe system analyzes the intake data and recommends a service package (Standard, Plus, or Premium) with estimated value.
-
SOW Can Be GeneratedFrom the intake data, a Statement of Work can be generated immediately, customized to the prospect's needs.
Discovery Assessment
The Discovery Assessment is a 12-question self-assessment wizard that prospects can complete anonymously. It detects Lens signals and generates risk analysis to qualify leads.
Assessment Flow
How to Use
-
Share the Discovery LinkShare discovery.html with prospects or embed it on the marketing site. No login required.
-
Prospect Selects ContextThe wizard asks whether the environment is cloud or datacenter, then adjusts terminology accordingly.
-
Answers Drive Signal DetectionEach answer triggers real-time Lens signal calculations for Q1-Q5 (Investment Misalignment, Process Dependency, Assumption Decay, Silent Accumulation, Visibility Gaps).
-
Results Show Risk ProfileAfter completing all questions, the prospect sees their risk profile with Q1-Q5 signal scores and an overall risk rating.
-
Lead CaptureOptionally capture email, name, company, and role. Completed sessions appear in the Sales Pipeline for follow-up.
-
Convert to ClientUse the convert endpoint to create a full client and assessment from the discovery data, preserving all signal analysis.
Lens Signals Detected
| Signal | Question | What It Detects |
|---|---|---|
| Investment Misalignment | Q1 | Security spend not aligned with actual risk |
| Process Dependency | Q2 | Critical processes relying on manual human behavior |
| Assumption Decay | Q3 | Outdated security assumptions still driving decisions |
| Silent Accumulation | Q4 | Risk growing quietly through deferred maintenance |
| Visibility Gaps | Q5 | Missing clarity that enables better security decisions |
Environment Profiling
The Environment Profiling wizard is a comprehensive 29-question assessment organized into 6 sections. It produces a maturity score, engagement recommendation, and market intelligence tags for existing clients.
Assessment Sections
| Section | Questions | Focus Area |
|---|---|---|
| Infrastructure & Architecture | 5 | Cloud, on-premises, hybrid environment details |
| Governance & Policy | 5 | Security governance, policies, compliance frameworks |
| Risk Management | 5 | Risk assessment, incident response, business continuity |
| Technical Controls | 5 | Network security, endpoint protection, access controls |
| Operational Security | 5 | Logging, monitoring, patching, vulnerability management |
| Compliance & Reporting | 4 | Regulatory requirements, audit readiness, reporting |
How to Use
-
Navigate to Environment DiscoveryOpen environment.html from the platform dashboard or client engagement tools.
-
Select the ClientChoose an existing client to profile. The profile is linked to the client record.
-
Complete 6-Section WizardWork through each section. Answers are partially saved as you progress, so you can resume later.
-
Review Maturity ScoreThe system calculates a 0-100 maturity score with four levels: Nascent (0-25), Developing (26-50), Established (51-75), Optimized (76-100).
-
Get Engagement RecommendationBased on maturity score and profile data, the system recommends the most appropriate service package (Security Advisory, Technology Strategy, Leadership Clarity, or Systems Diagnosis).
Outputs
ROI Calculator
The ROI Calculator generates three-scenario financial projections demonstrating the value of security investment, using industry-specific benchmarks.
How to Use
-
Navigate to ROI CalculatorOpen roi-calculator.html from the client engagement tools section of the dashboard.
-
Select IndustryChoose from 9 industries: Healthcare, Financial Services, Technology, Manufacturing, Retail, Government, Education, Energy, or Other. Each has industry-specific benchmarks.
-
Enter Company Size and MaturityInput employee count and current security maturity level. These factors adjust the calculation model.
-
Review Three ScenariosThe calculator generates Conservative, Expected, and Optimistic projections with year-over-year savings breakdown.
Projection Components
| Component | Description |
|---|---|
| Breach Cost Avoidance | Estimated savings from reducing breach probability |
| Incident Response Savings | Reduced incident response costs through improved detection |
| Compliance Efficiency | Reduced audit preparation and remediation costs |
| Operational Efficiency | Savings from reduced manual security processes |
Case Studies
Reference case studies from past engagements, filterable by Lens question, context, and industry. Use them during client conversations to illustrate the value of the Lens approach.
How to Use
-
Navigate to Case StudiesOpen case-studies.html from the client engagement tools section.
-
Filter by Lens QuestionSelect Q1-Q5 to find case studies relevant to specific systemic issues you're discussing with a client.
-
Filter by ContextFilter by cloud, datacenter, or hybrid to match the client's environment.
-
View OutcomesEach case study includes quantified outcomes (cost savings, time reduction, risk improvement) and engagement timeline.
Case Study Content
- Context: Industry, organization size, environment type
- Lens Questions: Which Q1-Q5 questions the engagement addressed
- Challenge: What systemic issues were identified
- Approach: How the Lens framework guided the engagement
- Outcomes: Quantified results with metrics
- Timeline: Engagement duration and key milestones
Sales Pipeline
The Sales Pipeline tracks leads from initial discovery through conversion to client. It integrates with Discovery sessions and the Intake Form to automatically create and qualify leads.
Pipeline Stages
| Stage | Description | Next Action |
|---|---|---|
| New | Lead created from Discovery, Intake Form, or manually | Review signals and qualify |
| Qualified | Lead has been reviewed and meets engagement criteria | Schedule call, generate SOW |
| Proposal | SOW has been generated and sent to prospect | Follow up on SOW |
| Negotiation | Active discussion on scope, pricing, or terms | Negotiate and finalize |
| Closed Won | Engagement confirmed, ready to convert | Convert to client |
| Closed Lost | Lead did not convert | Document reason, nurture |
How to Use
-
Navigate to PipelineOpen pipeline.html from the dashboard. The pipeline shows all leads with filtering by stage, source, and search.
-
Create LeadsLeads are created automatically from Discovery sessions, Intake Form submissions, or manually via the "New Lead" button. Sources include: discovery, intake_form, referral, website, and other.
-
Review Lead DetailsClick a lead to see contact info, company details, Discovery signals (if applicable), recommended package, and estimated value.
-
Update StageUse the stage selector to move leads through the pipeline. Stage changes are timestamped for tracking.
-
Generate SOWFrom the lead detail, generate a Statement of Work with signal-customized scope based on Discovery data.
-
Convert to ClientWhen a lead is won, click "Convert" to create a Client record and optionally an Assessment, preserving all lead data.
Pipeline Statistics
The pipeline dashboard shows key metrics:
- Total Pipeline Value: Sum of estimated values for active leads
- Conversion Rate: Percentage of leads that became clients
- Stage Distribution: Count of leads at each stage
- Average Deal Size: Mean estimated value of won deals
SOW Management
Generate, edit, and manage Statements of Work (SOWs) with automated content based on Discovery signals and package selection.
Available Packages
| Package | Duration | Description |
|---|---|---|
| Standard | 3-4 weeks | Core security assessment with Lens analysis and recommendations |
| Plus | 5-6 weeks | Standard + roadmap generation, GRC documents, and extended scope |
| Premium | 8-10 weeks | Comprehensive engagement with AI security, executive dashboard, and ongoing monitoring |
How to Use
-
Navigate to SOW ManagementOpen sow.html from the dashboard or from a lead's detail page.
-
Generate New SOWClick "Generate SOW" and select a lead and package. The system generates content based on Discovery signals, company profile, and package features.
-
Signal CustomizationIf the lead has Discovery data, the SOW automatically includes signal-specific scope items. For example, a strong Q4 signal adds patch velocity analysis to the scope.
-
Edit SOW ContentEdit individual sections (executive summary, scope, deliverables, timeline, pricing, terms) directly in the platform.
-
Update StatusTrack SOW through the workflow: Draft, Sent, Approved, Rejected, or Superseded.
-
Download PDFDownload the SOW as a branded PDF for sending to the client.
SOW Sections
- Executive Summary: High-level engagement overview tailored to the prospect
- Scope of Work: Detailed scope items, adjusted by Discovery signals
- Deliverables: List of deliverables by package tier
- Timeline: Week-by-week execution plan
- Pricing: Package pricing with optional add-ons
- Terms & Conditions: Standard engagement terms
Scoping & Planning
Proper scoping ensures the assessment delivers maximum value within the engagement parameters.
Assessment Types
| Type | Duration | Focus Areas |
|---|---|---|
| Rapid Assessment | 1-2 weeks | High-priority vulnerabilities, critical systems only |
| Standard Assessment | 3-4 weeks | Comprehensive review, all Lens questions, full remediation plan |
| Deep Dive Assessment | 6-8 weeks | Enterprise-wide, multiple business units, strategic roadmap |
Scoping Checklist
- Define in-scope systems, networks, and applications
- Identify out-of-scope areas and document exclusions
- Confirm testing windows and change freeze periods
- Establish communication channels and escalation paths
- Request API credentials for security tool integrations
- Schedule stakeholder interviews
- Define deliverable expectations and timeline
Conducting Interviews
Stakeholder interviews are essential for understanding context that automated scans cannot capture. Each Lens question should inform your interview approach.
Interview Preparation
-
Review Intake Form ResponsesUnderstand the organization's stated security posture, tools, and concerns before interviews.
-
Identify Key StakeholdersCISO/Security Lead, IT Operations, Development Lead, Business Unit Owners, Compliance/Risk Manager.
-
Prepare Role-Specific QuestionsTailor questions based on each stakeholder's domain and the Lens questions you need to explore.
-
Schedule 45-60 Minute SessionsAllow time for follow-up questions and note-taking. Record sessions with permission.
Lens-Aligned Interview Questions
- "What metrics does leadership use to evaluate security program success?"
- "Where do you feel security budget is well-spent? Where might it be misallocated?"
- "How do security investments align with business objectives?"
- "Walk me through how a developer deploys code to production."
- "What happens when someone reports a phishing email?"
- "How do you ensure security policies are followed consistently?"
- "What security decisions were made years ago that you've never revisited?"
- "How has your threat landscape changed since your last major security review?"
- "Are there controls in place that no one really understands anymore?"
- "What security issues tend to get deprioritized repeatedly?"
- "Where do you have technical debt that affects security?"
- "Are there alerts or logs that nobody monitors regularly?"
- "What security processes feel overly complicated?"
- "Where do people work around security controls to get their jobs done?"
- "What information would help teams make better security decisions?"
Documenting Interview Findings
After each interview:
- Create findings in the platform for each identified issue
- Tag findings with the relevant Lens question (Q1-Q5)
- Note direct quotes that illustrate systemic issues
- Identify follow-up items requiring documentation or technical validation
Performing Security Scans
The Lens Platform integrates with multiple security scanning tools and supports importing results from 19+ scanner formats.
Supported Scanner Formats
| Category | Scanners |
|---|---|
| Vulnerability Scanners | Nessus, Qualys, Rapid7 InsightVM, OpenVAS, Tenable.io |
| SAST/DAST | Snyk, Checkmarx, Veracode, Fortify, SonarQube |
| Cloud Security | Wiz, Orca, Prisma Cloud, AWS Inspector, Azure Defender |
| Container Security | Trivy, Anchore, Aqua Security |
| Generic | CSV import with custom field mapping |
Scan Coordination Best Practices
-
Coordinate Timing with ClientSchedule scans during low-traffic periods. Avoid change freeze windows and critical business operations.
-
Document Scan ConfigurationRecord scan policies, credentials used, and excluded targets. This ensures reproducibility and audit trail.
-
Run Authenticated ScansCredentialed scans provide deeper visibility. Coordinate with IT to obtain appropriate service accounts.
-
Export Results PromptlyExport scan results in supported formats (JSON, CSV, native) immediately after completion for import.
API Connector Setup
Connect directly to client security tools to automatically pull findings into your assessment.
Adding a Connector
-
Navigate to Assessment SettingsOpen the assessment and click the Settings icon or navigate to the Connectors tab.
-
Select Connector TypeChoose from available integrations: Snyk, Wiz, or custom API connectors.
-
Enter API CredentialsProvide the API key, organization ID, and any required configuration. Credentials are encrypted at rest.
-
Test ConnectionClick "Test Connection" to verify the credentials work before saving.
-
Configure Sync SettingsSet filters for which projects/resources to sync and the sync frequency.
Snyk Integration
Pull application security findings directly from the client's Snyk organization.
Obtaining Snyk API Credentials
The client needs to provide:
- API Token: Found in Snyk Account Settings > General > Auth Token
- Organization ID: Found in Organization Settings > General (UUID format)
What Gets Imported
| Data Type | Description |
|---|---|
| Open Source Vulnerabilities | Dependency vulnerabilities with CVSS scores, fix availability |
| Code Security Issues | SAST findings from Snyk Code analysis |
| Container Vulnerabilities | Image vulnerabilities from Snyk Container |
| IaC Misconfigurations | Infrastructure as Code issues from Snyk IaC |
// Example Snyk API configuration
{
"connector_type": "snyk",
"api_token": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"org_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"severity_threshold": "medium" // low, medium, high, critical
}
Wiz Integration
Import cloud security findings from Wiz's Cloud Security Posture Management (CSPM) platform.
Obtaining Wiz API Credentials
The client needs to generate a Service Account:
-
Create Service Account in WizNavigate to Settings > Service Accounts > Create Service Account. Assign "Read" permissions.
-
Copy Client ID and Client SecretSave both values securely - the secret is only shown once during creation.
-
Note the API Endpoint URLWiz has regional endpoints. Confirm which endpoint the client's tenant uses.
What Gets Imported
| Data Type | Description |
|---|---|
| Cloud Misconfigurations | CSPM findings across AWS, Azure, GCP |
| Vulnerabilities | Host and container vulnerabilities with context |
| Secrets Exposure | Detected secrets in code and configurations |
| Network Exposure | Internet-exposed resources and paths |
Importing Scan Data
For tools without direct API integration, import scan results using file uploads.
Import Process
-
Navigate to Import PageFrom the assessment, click "Import Scan" or navigate to import-scan.html
-
Select Scanner TypeChoose the source scanner from the dropdown. This determines parsing logic.
-
Upload FileDrag and drop or click to select the export file. Supported: JSON, CSV, XML (scanner-specific)
-
Map Fields (CSV only)For generic CSV imports, map columns to vulnerability fields: title, severity, description, CVE, etc.
-
Review and ConfirmPreview imported findings, check for parsing issues, then confirm import.
Finding Review Workflow
The review workflow ensures every finding is validated, contextualized, and actionable before inclusion in deliverables.
Finding States
| Status | Description | Action |
|---|---|---|
| Pending | Newly imported, awaiting consultant review | Review and classify |
| Accepted | Confirmed as valid finding, included in report | Generate recommendation |
| Modified | Adjusted severity, description, or classification | Document rationale |
| Rejected | False positive or out of scope | Document rejection reason |
Review Process
-
Open Review PageNavigate to review.html from the assessment. Findings are listed by severity.
-
Select a FindingClick on a finding to view details, evidence, and scanner output in the right panel.
-
Validate the FindingConfirm the vulnerability exists, assess actual severity in context, identify affected assets.
-
Map to Lens QuestionAssign the finding to Q1-Q5 based on the systemic issue it represents. This enables pattern detection.
-
Set StatusAccept, modify, or reject the finding. Add comments explaining any modifications.
-
Add EvidenceAttach screenshots, logs, or documentation supporting the finding.
Cybersecurist Lens™ Framework
The Lens framework identifies systemic security issues through five strategic questions. Mapping findings to these questions enables pattern detection and strategic recommendations.
Signal Type: Investment Misalignment
Indicators: Security spend not aligned with risk, compliance-driven rather than risk-driven decisions, metrics that don't measure actual security outcomes.
Example Finding: Organization has expensive SIEM but no one reviews alerts; budget for endpoint protection but no vulnerability management program.
Signal Type: Process Dependency
Indicators: Manual processes for critical security functions, policies that assume 100% compliance, no technical enforcement of procedures.
Example Finding: Code review policy exists but no branch protection; phishing training without technical email filtering; manual key rotation.
Signal Type: Assumption Decay
Indicators: Outdated network diagrams, legacy trust relationships, controls designed for previous architecture, "we've always done it this way" thinking.
Example Finding: Firewall rules from 2018 that reference decommissioned systems; VPN as primary access when most apps are now SaaS.
Signal Type: Silent Accumulation
Indicators: Deferred patching, growing exception lists, ignored alerts, accumulating technical debt, "temporary" solutions that became permanent.
Example Finding: 500+ systems with critical patches pending for >90 days; 200 firewall exception rules that "we'll clean up later."
Signal Type: Visibility Gaps
Indicators: Unknown assets, shadow IT, lack of data classification, complex processes no one understands, missing documentation.
Example Finding: No complete asset inventory; developers don't know which data is sensitive; incident response plan exists but untested.
AI-Powered Recommendations
The platform uses Claude AI to generate comprehensive, context-aware recommendations for each finding.
Recommendation Dimensions
Generating Recommendations
-
Accept the FindingOnly accepted findings can have recommendations generated. Review and set status first.
-
Click "Generate Recommendation"In the finding detail panel, click the generate button. The AI analyzes the finding with assessment context.
-
Review Generated ContentReview all four dimensions, implementation steps, success metrics, and effort estimate.
-
Edit as NeededModify any section to add client-specific context or adjust recommendations based on your expertise.
-
Mark as ReviewedSet "Analyst Reviewed" flag to indicate human validation of the AI-generated content.
Vulnerability Prioritization
The platform uses a sophisticated algorithm to prioritize vulnerabilities beyond just CVSS scores.
Prioritization Factors
| Factor | Weight | Description |
|---|---|---|
| CVSS Score | 30% | Base technical severity from the CVE database |
| Asset Criticality | 25% | Business importance of affected systems (critical, high, medium, low) |
| Exploit Availability | 20% | Known exploits in the wild, Metasploit modules, PoC code |
| Lens Signals | 25% | Systemic risk indicators from Lens framework mapping |
Using the Vulnerabilities Page
Navigate to vulnerabilities.html to access the prioritized vulnerability view:
- Filter by severity: Focus on Critical/High first
- Sort by priority score: Combined algorithm score
- Group by asset: See which systems need most attention
- Track remediation status: Open, In Progress, Resolved, Risk Accepted
Assessment Reports
Generate comprehensive Word document reports containing all findings, recommendations, and remediation guidance.
Report Contents
- Executive Summary with key metrics and risk overview
- Findings organized by Lens question with systemic analysis
- Detailed recommendations with implementation steps
- Vulnerability inventory with prioritization scores
- Remediation roadmap with effort estimates
- Appendices with technical details and evidence
Generating Reports
-
Complete Finding ReviewEnsure all findings have been reviewed and have status set. Generate recommendations for accepted findings.
-
Navigate to AssessmentOpen the assessment from the Dashboard and click "Generate Report" in the actions menu.
-
Select Report OptionsChoose which sections to include, level of detail, and any custom branding requirements.
-
Generate and DownloadClick Generate. The report is created as a .docx file and downloaded automatically.
Executive Briefings
Create board-ready presentations summarizing assessment findings for executive audiences.
Briefing Format
Executive briefings are designed for 15-20 minute presentations covering:
- Overall security posture assessment (risk rating)
- Top 3-5 systemic risks requiring attention
- Business impact analysis in financial terms
- Recommended immediate actions
- 90-day remediation priorities
Using the Briefing Generator
-
Navigate to BriefingsFrom the assessment, click "Executive Briefing" or go to briefing/index.html
-
Select Findings to HighlightChoose 3-5 critical findings that represent systemic issues for executive attention.
-
Customize MessagingAdjust the business context, industry comparisons, and recommended actions.
-
Generate BriefingThe AI generates executive-appropriate language and talking points.
-
ExportDownload as PDF or copy to your presentation tool of choice.
Security Roadmaps
Generate comprehensive multi-year security roadmaps with phased execution plans, NIST CSF and CIS Controls alignment, and four-dimensional action items.
Roadmap Phases
| Phase | Timeframe | Focus |
|---|---|---|
| Quick Wins | 0-3 months | High-impact, low-effort improvements that build momentum |
| Foundation | 3-12 months | Core security program elements, policy development, tool deployment |
| Maturity | 12-24 months | Process optimization, advanced controls, team development |
| Optimization | 24-36 months | Continuous improvement, automation, advanced threat detection |
| Continuous | 36+ months | Ongoing monitoring, adaptation, and maturity advancement |
How to Use
-
Navigate to Roadmap ToolOpen roadmap.html from the dashboard deliverables section.
-
Generate RoadmapSelect a client and assessment. The generator uses organization size, industry, maturity level, and Lens signals to create a tailored multi-year plan.
-
Review Phases and ActionsEach phase contains categorized actions (Technical, Organizational, Operational, Strategic) with effort estimates, NIST/CIS mappings, and Lens alignment.
-
Track ExecutionUpdate action status (Not Started, In Progress, Completed, Blocked, Deferred) to track progress. Use bulk status update for efficiency.
-
Analyst ReviewMark the roadmap as analyst-reviewed to indicate human validation of the AI-generated plan.
Action Categories
Framework Alignment
Each action is mapped to relevant frameworks:
- NIST CSF 2.0: Govern, Identify, Protect, Detect, Respond, Recover
- CIS Controls v8.1: Mapped to specific control numbers
- Lens Framework: Q1-Q5 alignment and signal addressed
GRC Documents
Generate, manage, and export governance, risk, and compliance documents from a library of templates covering 7+ compliance frameworks.
Document Types
| Type | Description | Examples |
|---|---|---|
| Policy | High-level organizational directives | Information Security Policy, Access Control Policy |
| Procedure | Step-by-step operational instructions | Incident Response Procedure, Change Management |
| Standard | Technical requirements and configurations | Password Standard, Encryption Standard |
| Guideline | Recommended practices and guidance | Secure Development Guidelines |
| Charter | Committee and program mandates | Security Steering Committee Charter |
Supported Frameworks
How to Use
-
Navigate to GRC DocumentsOpen grc-documents.html from the dashboard. The page has four tabs: Documents, Templates, Packages, and Compliance Matrix.
-
Browse TemplatesFilter templates by document type, category, or framework. Each template shows applicable frameworks, estimated pages, and review frequency.
-
Generate Single DocumentSelect a template and generate a document for a client. The generator uses client context (industry, maturity, applicable frameworks) to customize content.
-
Generate Document PackageUse pre-defined packages (e.g., "SOC 2 Essential", "ISO 27001 Core") to generate multiple related documents at once.
-
Edit SectionsEach generated document has editable sections. Update content to reflect client-specific details and requirements.
-
Approve and ExportRoute through the approval workflow (Draft, Review, Approved, Active, Archived). Export as PDF or Markdown.
Compliance Tools
- Compliance Matrix: View framework coverage across all documents for a client, identifying which controls are addressed
- Gap Analysis: Identify missing documents and unaddressed framework requirements
- Version History: Track all changes to documents with version snapshots and change summaries
- Recommended Packages: AI-driven package recommendations based on client context and compliance gaps
Document Workflow
SLA Management
Define and enforce remediation deadlines with policy-based SLA tracking and automated escalation alerts.
Creating SLA Policies
SLA policies define remediation timeframes based on vulnerability severity and asset criticality:
| Severity | Default Response | Default Remediation |
|---|---|---|
| Critical | 4 hours | 24 hours |
| High | 24 hours | 7 days |
| Medium | 72 hours | 30 days |
| Low | 1 week | 90 days |
Escalation Workflow
-
Warning Alert (75% of SLA)Notification sent to assigned owner when 75% of remediation time has elapsed.
-
Breach Alert (100% of SLA)SLA violation recorded, escalation notification sent to management channels.
-
Critical Escalation (125% of SLA)Executive notification triggered for unresolved critical/high severity items.
Ticket Integration
Automatically create and synchronize remediation tickets with Jira and ServiceNow for streamlined vulnerability management.
Supported Platforms
Configuration
-
Navigate to Ticket IntegrationsGo to Client Settings > Integrations > Ticket Systems.
-
Add IntegrationSelect Jira or ServiceNow, enter base URL, and provide API credentials.
-
Configure MappingMap Lens priority scores to ticket priorities and select default project/queue.
-
Enable Auto-Create (Optional)Automatically create tickets for new vulnerabilities above a severity threshold.
Bidirectional Sync
Ticket status changes are synchronized back to Lens via webhooks:
- Ticket closed → Triggers patch verification
- Verification passes → Vulnerability marked remediated
- Verification fails → Ticket reopened with comment
Threat Intelligence
Enrich vulnerability data with real-time threat intelligence from CISA KEV and EPSS for improved prioritization.
Intelligence Sources
| Source | Data Provided | Update Frequency |
|---|---|---|
| CISA KEV | Known exploited vulnerabilities, required action date | Daily (auto-cached 24h) |
| EPSS | Exploitation probability score (0-1), percentile ranking | Daily (auto-cached 24h) |
Enrichment Process
-
Automatic EnrichmentNew vulnerabilities are automatically enriched with KEV/EPSS data on import.
-
Manual Bulk EnrichmentRe-enrich existing vulnerabilities via Assessment Actions > Enrich Threat Intel.
-
Priority Score UpdatePriority scores are recalculated incorporating KEV (+10 boost) and EPSS factors.
Notification Channels
Configure multi-channel notifications for SLA alerts, verification results, and security updates.
Supported Channels
Alert Levels
| Level | Use Cases |
|---|---|
| Info | Status updates, completed actions, informational messages |
| Warning | SLA approaching, verification needed, attention required |
| Breach | SLA violated, verification failed, escalation triggered |
| Critical | KEV alert, critical vulnerability detected, immediate action required |
Channel Configuration
-
Navigate to NotificationsGo to Client Settings > Notification Channels.
-
Add ChannelSelect channel type and provide configuration (webhook URL, SMTP settings, etc.).
-
Set Minimum Alert LevelConfigure which alert levels trigger notifications on this channel.
-
Test ChannelSend a test notification to verify configuration is correct.
Executive Dashboard
Real-time strategic visibility into security posture with Lens scores, remediation velocity, and compliance metrics.
Dashboard Components
Top Risks View
Prioritized list of the most critical vulnerabilities based on:
- CISA KEV status (known exploited)
- EPSS score (exploitation probability)
- Asset criticality and business context
- Dwell time (days since detection)
- SLA violation status
Snapshot History
Daily snapshots capture metrics for historical trend analysis. Snapshots are automatically captured at midnight UTC and include all dashboard metrics for point-in-time comparison.
Early Warning System
Proactive detection of security posture degradation through pattern analysis and anomaly detection.
Detection Patterns
| Pattern | Threshold | Severity |
|---|---|---|
| Signal Increase | 25% increase in Lens signals week-over-week | Medium/High |
| Dwell Time Alert | Critical/High vulnerabilities open >45 days | High/Critical |
| Recurrence Pattern | Same vulnerability detected 3+ times | Medium |
| Trend Degradation | Lens score dropped 5+ points in 30 days | High |
| KEV Alert | New CVE added to CISA KEV matching asset | Critical |
Alert Workflow
-
DetectionScheduled analysis runs every 4 hours scanning for patterns across all active assessments.
-
Alert CreationDetected patterns create early warning alerts with severity, details, and recommendations.
-
NotificationAlerts trigger notifications via configured channels based on severity.
-
ResolutionAlerts can be dismissed with reason or automatically resolve when condition clears.
Patch Verification
Validate that remediation actions are effective by comparing scan results before and after patching.
Verification Triggers
- Ticket Webhook: Automatically triggered when Jira/ServiceNow ticket is closed
- Manual: Consultant-initiated verification from vulnerability details
- Scheduled: Periodic verification of recently remediated items
Verification Process
-
Trigger VerificationVerification is triggered via webhook, manual action, or schedule.
-
Compare Scan ResultsSystem compares latest scan data against the vulnerability's original detection.
-
Determine OutcomeIf vulnerability no longer detected → Remediated. If still present → Failed.
-
Take ActionSuccess: Mark as remediated. Failure: Reopen ticket, send notification.
Verification History
All verification attempts are logged for audit purposes with:
- Timestamp and trigger source
- Verification outcome (remediated/still present)
- Scan source used for verification
- Actions taken (ticket reopened, notification sent)
AI Security Platform
The AI Security Platform provides comprehensive AI/ML security assessment capabilities integrating 7 major frameworks for identifying and mitigating AI-specific risks.
Tiered Offering
| Tier | Features | Target Audience |
|---|---|---|
| Free | AI Discovery - 15-question wizard with framework signal analysis | Prospects exploring AI security needs |
| Standard | AI Assessment - 50-question comprehensive evaluation with maturity scoring | Clients needing detailed AI security assessment |
| Premium | AI Dashboard - Trending, compliance timeline, red team results | Enterprise clients with continuous monitoring needs |
Integrated Frameworks
AI Discovery (Free Tier)
The AI Discovery tool provides anonymous prospects with a quick AI security assessment, detecting framework signals and capturing leads for conversion.
Assessment Flow
Framework Signal Detection
Each answer triggers signal calculations for:
- OWASP LLM Signals - Maps to specific LLM01-LLM10 vulnerabilities
- MITRE ATLAS Signals - Identifies relevant tactics and techniques
- EU AI Act Risk Level - Classifies as unacceptable, high, limited, or minimal
- Governance Signals - Detects policy, oversight, and documentation gaps
API Endpoints
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/ai-discovery/start | Start anonymous session with AI maturity context |
| POST | /api/ai-discovery/{session}/answer | Submit answer with real-time signal calculation |
| GET | /api/ai-discovery/{session}/results | Get framework scores and risk analysis |
| POST | /api/ai-discovery/{session}/complete | Complete with lead capture (email, name, company) |
| POST | /api/ai-discovery/{session}/convert | Convert to authenticated AI Security Profile |
AI Assessment (Standard Tier)
The AI Security Assessment provides comprehensive 50-question evaluation across all 7 frameworks, generating maturity scores and detailed compliance readiness metrics.
Assessment Sections
| Section | Questions | Focus Area |
|---|---|---|
| AI Inventory | Q1-Q10 | AI system count, types, LLM providers, deployment models |
| Governance | Q11-Q20 | AI policy, oversight committee, model inventory, documentation |
| Risk Management | Q21-Q30 | NIST AI RMF alignment, risk assessment processes |
| Technical Controls | Q31-Q40 | Prompt injection, output filtering, supply chain vetting |
| Compliance | Q41-Q45 | EU AI Act readiness, ISO 42001 alignment |
| Monitoring | Q46-Q50 | Model behavior monitoring, incident response, red teaming |
Maturity Scoring
The assessment calculates a 0-100 maturity score with four levels:
- Nascent (0-25) - Ad-hoc AI usage with minimal security controls
- Developing (26-50) - Basic governance and emerging technical controls
- Established (51-75) - Formal AI security program with framework alignment
- Optimized (76-100) - Continuous improvement with advanced threat detection
Framework Scores
Individual scores calculated for each framework:
- OWASP LLM Score - Coverage against LLM Top 10 vulnerabilities
- OWASP Agentic Score - Coverage for agentic AI risks
- MITRE ATLAS Coverage - Percentage of tactics with controls
- NIST AI RMF Alignment - Govern, Map, Measure, Manage scores
- EU AI Act Readiness - Compliance percentage with deadline tracking
- ISO 42001 Readiness - Management system alignment
- Gartner MCP Score - Position on 5-step maturity journey
API Endpoints
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/ai-security/start | Start profile for authenticated client |
| POST | /api/ai-security/{profile}/answer | Submit answers with partial save support |
| GET | /api/ai-security/{profile}/maturity | Get maturity score and level |
| GET | /api/ai-security/{profile}/owasp | Get OWASP LLM coverage details |
| GET | /api/ai-security/{profile}/atlas | Get MITRE ATLAS coverage |
| GET | /api/ai-security/{profile}/compliance | Get EU AI Act and ISO 42001 readiness |
| POST | /api/ai-security/{profile}/complete | Complete and calculate all framework scores |
AI Dashboard (Premium Tier)
The AI Security Dashboard provides continuous monitoring, historical trending, and red team result tracking for enterprise clients.
Dashboard Features
Metric Snapshots
Periodic snapshots capture point-in-time metrics for trending analysis:
- Overall maturity score and level
- Framework scores (OWASP, ATLAS, NIST, EU AI Act)
- Control implementation count and coverage percentage
- Days remaining to EU AI Act compliance deadline
Red Team Integration
Track AI-specific security testing results:
| Test Type | ATLAS Mapping | OWASP Mapping |
|---|---|---|
| Prompt Injection | AML.T0051 | LLM01 |
| Jailbreak Attempts | AML.T0054 | LLM01, LLM09 |
| Data Extraction | AML.T0024 | LLM06 |
| Model Inversion | AML.T0025 | LLM06 |
| Supply Chain | AML.T0010 | LLM05 |
API Endpoints
| Method | Endpoint | Description |
|---|---|---|
| GET | /api/ai-dashboard/{profile}/overview | Full dashboard metrics and scores |
| GET | /api/ai-dashboard/{profile}/trend | Historical trend data (6-12 months) |
| GET | /api/ai-dashboard/{profile}/owasp-coverage | OWASP radar chart data |
| GET | /api/ai-dashboard/{profile}/compliance-timeline | EU AI Act deadline tracking |
| POST | /api/ai-dashboard/{profile}/snapshot | Capture metrics snapshot |
| GET | /api/ai-dashboard/{profile}/red-team-results | List red team test results |
| POST | /api/ai-dashboard/{profile}/red-team | Submit red team test result |
Framework Reference
Quick reference for the 7 AI security frameworks integrated into the platform.
OWASP LLM Top 10 2025
| ID | Vulnerability | Description |
|---|---|---|
| LLM01 | Prompt Injection | Manipulating LLM behavior through crafted inputs |
| LLM02 | Insecure Output Handling | Failing to validate/sanitize LLM outputs |
| LLM03 | Training Data Poisoning | Corrupting training data to influence model behavior |
| LLM04 | Model Denial of Service | Resource exhaustion attacks against LLM systems |
| LLM05 | Supply Chain Vulnerabilities | Risks from third-party models and components |
| LLM06 | Sensitive Information Disclosure | Exposing confidential data through model outputs |
| LLM07 | Insecure Plugin Design | Vulnerabilities in LLM plugin/extension systems |
| LLM08 | Excessive Agency | Granting LLMs too much autonomy or capability |
| LLM09 | Overreliance | Trusting LLM outputs without verification |
| LLM10 | Model Theft | Unauthorized access or extraction of model weights |
Gartner CISO MCP 2026 Journey
-
Step 1: ReactiveAd-hoc AI usage with no formal security controls or governance.
-
Step 2: AwareRecognition of AI risks with initial policy development.
-
Step 3: ProactiveFormal AI security program with defined controls and processes.
-
Step 4: ManagedComprehensive governance with continuous monitoring and metrics.
-
Step 5: OptimizingContinuous improvement with advanced threat detection and response.
EU AI Act Risk Classification
| Risk Level | Requirements | Examples |
|---|---|---|
| Unacceptable | Prohibited - cannot be deployed in EU | Social scoring, real-time biometric ID |
| High | Strict requirements: conformity assessment, documentation, human oversight | Hiring AI, credit scoring, medical devices |
| Limited | Transparency obligations | Chatbots, deepfake detection |
| Minimal | No specific requirements | AI-enabled games, spam filters |
NIST AI RMF Functions
Client Portal
The Client Portal provides a self-service interface for clients to view their engagement status, deliverables, findings, and remediation progress. Clients access the portal via invite-only authentication with their own dedicated login.
Portal Pages
| Page | URL | Purpose |
|---|---|---|
| Client Login | /client/login.html |
Dedicated client authentication portal |
| Accept Invite | /client/accept-invite.html |
New client onboarding — set password and activate account |
| Client Portal | /client/portal.html |
Main 5-tab self-service hub |
| Password Reset | /client/reset-password.html |
Client password recovery |
Client Invite Flow
Consultants generate invite links from the Pipeline or Client detail views. Clients receive the link (shared manually), accept the invitation, set their password, and are automatically logged into the portal.
-
Generate InviteFrom Pipeline or Dashboard, click "Invite to Portal" on a converted lead/client. Enter the client's email address.
-
Share LinkCopy the generated invite URL and share it with the client via email or secure messaging. Links expire after 7 days.
-
Client AcceptsClient opens the link, sees the invitation details (client name, email), enters their full name, and sets a password meeting the security policy.
-
Portal AccessOn acceptance, the client is automatically logged into the portal. The Executive tab loads by default showing their security posture.
Portal Tabs
The portal provides five tabs, each lazy-loaded on first access for performance. The Executive tab is the default view.
| Tab | Content | Key Features |
|---|---|---|
| Executive (default) | Lens score radar, trend charts, top risks, early warnings | Real-time security posture overview |
| Overview | Engagement status, assessment summaries, active SOW, recent activity | Engagement health at a glance |
| Deliverables | SOWs, roadmaps, GRC documents, assessment reports | View, download, approve/reject |
| Findings | Security findings filtered by assessment, severity, Lens question | Expandable detail with recommendations and comments |
| Remediation | Vulnerability counts by status, roadmap progress, SLA compliance | Track remediation progress over time |
Consultant Actions
Consultants can interact with the client portal from the main platform:
- View client comments on findings and deliverables from the Review and SOW pages
- Reply to comments via the consultant reply endpoint (can mark as internal-only)
- Monitor approvals — see when clients approve or request revisions on deliverables
- Manage invitations — view, resend, or revoke portal invitations from the client detail view
User Management
Manage consultant and administrator access to the platform.
User Roles
| Role | Permissions |
|---|---|
| Administrator | Full access: user management, all assessments, system settings |
| Consultant | Create/edit assessments, manage findings, generate reports |
| Viewer | Read-only access to assigned assessments |
| Client | Portal-only access: own engagement data, deliverables, findings, comments |
Adding Users
-
Navigate to Admin PanelClick on your user avatar and select "Admin" or navigate to the administration section.
-
Click "Add User"Enter email, name, and select the appropriate role.
-
Set Initial PasswordThe system generates a temporary password. User must change on first login.
Platform Settings
Configure global platform settings and integration defaults.
Available Settings
- AI Provider Configuration: Anthropic API key for recommendations
- Default Connector Settings: Pre-configured integration parameters
- Report Templates: Customizable report headers, footers, branding
- Notification Preferences: Email alerts for assessment milestones