Collect
Normalize public and private-source evidence into consistent intelligence objects.
Product
Hidden Intel is structured around evidence, signals, and assessments so vulnerability and threat activity can be understood in operational context.
Product model
Hidden Intel is designed for operational security teams who need to explain why an item moved and what to do next.
Normalize public and private-source evidence into consistent intelligence objects.
Evaluate source quality, velocity, novelty, recurrence, and relevance.
Surface items with transparent reasons rather than collapsing context into one opaque score.
Route attention through watchlists, assets, saved searches, alert policies, briefs, and API workflows.
Capabilities
Capabilities are designed for production use, with gated, preview, and planned states supported in the interface until backend integration is complete.
Context for vulnerability activity, history, severity drivers, and product relevance.
Clear distinction between observed exploitation and exploit availability.
Public capability signals such as PoCs, exploit code, modules, and detection templates.
Zero-day status follows backend semantics and is never inferred from exploit code alone.
Security signals that may exist before a complete canonical CVE record.
Corroborated clusters forming across independent sources and source types.
Indicator context designed for authenticated workflows rather than anonymous bulk exposure.
Vendor, product, and family movement with history and recurrence context.
A broader view of acceleration, momentum, exposure, and intelligence movement.
Tracked products, vendors, topics, and vulnerabilities for focused monitoring.
Exposure-aware context for assets and products that matter to the organization.
Reusable intelligence queries for recurring analyst and vulnerability workflows.
Policy-driven notifications for threshold, signal, and entitlement-aware events.
Briefing-style summaries with evidence, signal, and assessment separation.
Server-side integration path for authorized customers and internal products.
Curated intelligence delivery for authenticated and entitled use cases.
Semantic discipline
The UI keeps confidence, evidence, availability, exploitation, and watch states separate so teams can act without ambiguity.
The public preview does not call the production intelligence API, does not embed credentials, and does not expose authenticated datasets.
Watch states represent monitor-worthy movement with lower urgency or corroboration, never a claim that exploitation is underway.
Hot intelligence reflects acceleration, new corroboration, or fast-moving relevance. It is not a universal severity score.
Pulse
Designed to show current priority, recent activity, observed exploitation, exploit availability, Early Alerts, emerging clusters, watch signals, IOC movement, and vendor/product movement.
A bounded presentation state showing the intelligence categories Hidden Intel can surface after authenticated access is connected.
Public capability
Example row showing how proof-of-concept, module, or detection artifacts would be separated from exploitation evidence.
Authority-backed
Example row for exploitation evidence such as canonical exploited-in-the-wild reporting or KEV-style authority signals.
Pre-canonical signal
Example row for security activity that may form before a complete CVE record exists.
Premium feeds, API access, and custom webhooks show upgrade states instead of failing silently.
Customer assets are sensitive and are not represented with fabricated inventory in this phase.
A production integration error should preserve context and provide a safe retry path.