B

Zero Trust Self-Assessment Kit

3.45

Derivation Chain

Step 1 Large-scale federal data breach incidents
→
Step 2 Demand for strengthened cybersecurity systems
→
Step 3 Zero Trust architecture adoption support
→
Step 4 SME Zero Trust maturity self-assessment and roadmap SaaS

Competitor references

No usable source links are available for this idea. Its signal notes and scores need independent verification.

Problem

Following the Korean government's Zero Trust guidelines announcement, mid-sized companies (100-300 employees) are evaluating adoption, but security consulting firms charge $22,500-$60,000 for current security posture assessments and roadmap development. Most IT teams don't know where to begin.

Solution

(1) Assess current maturity across 5 levels using a 40-item self-assessment questionnaire based on KISA (Korea Internet & Security Agency) Zero Trust guidelines, (2) auto-generate a 12-month roadmap with industry- and size-specific priority adoption areas (network/identity/data) and budget ranges, and (3) track progress through quarterly re-assessments.

Target: IT team leads/CISOs at mid-sized companies with 100-300 employees, and security consultants
Revenue Model: SaaS Monthly Subscription at ~$59/month per organization (assessment + roadmap + quarterly re-assessment), one-time diagnostic Report at ~$225 Per Transaction
Ecosystem Role: Education
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
2.0/5
U Urgency
3.0/5
M Market
3.0/5
R Realizability
5.0/5
V Validation
3.0/5
NUMR-V Scoring System
N Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation signal quality from competition and demand data.
N=.15 U=.20 M=.15 R=.30 V=.20

Feasibility (78%)

Tech Complexity
34.7/40
Data Availability
23.1/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.

Market Validation (56/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
16.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
5.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.

Technical Requirements

Backend [medium] Frontend [low] AI/ML [low]
Dashboard