Slack
Notifications to your chosen channels.
Identify vulnerabilities affecting your inventory, prioritise them and track remediation. Manage threat intelligence and research in the same panel.
Kullandığınız ürün ve sürümlere odaklanın.
KEV, EPSS ve varlık bilgisiyle değerlendirin.
İlgili bulguyu sorumlu ekibe iletin.
Aksiyonu ve uygulanan çözümü kaydedin.
Choose a screen to explore that part of the product and how to use it.
Define the products you use, their installed versions and responsible teams. Assess published vulnerabilities in that context.
Review CVSS, CISA KEV and EPSS alongside asset criticality and internet exposure. Set priorities according to your organisation's circumstances.
Add an assignee, due date and action note to a finding. Track overdue work, pending reviews and completed remediation in the same workflow.
Import your software bill of materials and review package matches against OSV records. Use manual uploads or CI imports for components.
Monitor public status sources for your selected service providers. Configure team notifications for status changes, outages and recoveries.
Choose a topic group to explore the tools and application screens.
Investigate malicious and suspicious URLs, domains and IPs with source, status and date information. Narrow your review list using filters and summary charts.
Review shared threat indicators and company-specific IOCs in one workspace. Define your company sector, monitored domains and networks, and indicator validity periods.
Review brand similarity and character impersonation indicators in active threat feeds. Define your official domain, and add reasons and assessments to similar-domain findings.
Map IOCs and inventory findings to MITRE ATT&CK techniques. Record analyst assessments of your company's logging, detection rules and test coverage.
Review MITRE ATT&CK actor and campaign profiles alongside techniques, malware and source versions. Sector information is shown when available at the source.
Compare two SBOM uploads for the same application. Assess added, removed and changed components alongside current CVE and OSV matches.
Review EPSS increases, additions to KEV and affected-version changes with their old and new values. Assess notifications in the panel and mark them reviewed.
Monitor DNS, HTTPS certificates and new subdomains observed in certificate transparency records for domains verified with a TXT record. Review unexpected changes.
Review sources and change history for CVEs, IOCs, vendor advisories and actor profiles. Source withdrawals are visible; private IOC history stays within the company scope.
Collect hypotheses, required logs, queries and results in a research record. Create new work from previous research and review edit history.
Review public KVKK data breach announcements by date range. Access the latest announcements from Overview, and follow new announcements using notification preferences.
Add product impact assessments to findings using OpenVEX documents. Record remediation evidence and versions; verify remediation or reopen the finding if verification fails.
Assign assets to responsible teams and configure team notifications. Track management report preparation in the history and download completed reports again.
Inventory, research and private indicators are scoped to a company. Viewing and editing follow the user's role; sign-in includes email verification.
Screens contain sample data. Organisations and announcements in the KVKK image are illustrative.
Imagine a firewall in your inventory. When a new record for that product arrives, the process follows these steps.
A newly published vulnerability is imported during a scheduled source check.
Product and version details are compared. KEV, EPSS and asset criticality are assessed.
The relevant team receives findings according to its preferences; an assignee and due date are set.
An update or other action is applied; remediation evidence and the new version are recorded.
Explore examples of vulnerability, inventory, daily summary and service notifications.
A new critical CVE record, its scores and verification steps.
Affected asset, high severity, KEV details and recommended actions.
Details of a medium-severity vulnerability and information to check the product.
A low-severity CVE record and suggested verification steps.
Daily summary of severity distribution, priority findings and service statuses.
Information to check the provider issue and its impact.
Service recovery details and workflows to verify within your organisation.
Send notifications through configured connections and create work items for findings.
Notifications to your chosen channels.
Notifications in your team's workspace.
Send events to your own systems.
Create work items for findings.
Track findings through work items.
Sources are checked regularly. New records enter the matching and notification process after import.
Attack techniques, actors and campaign relationships
Malicious and suspicious indicators from active sources
crt.sh for subdomain observations of verified domains
CVE records, descriptions and product/version information
Vulnerabilities known to be actively exploited
Scores estimating vulnerability exploitation probability
Security advisories from supported vendors
Vulnerability records for software packages and dependencies
Public data breach announcements
PDF reports summarise severity distribution, KEV information, asset counts and priority open findings.
Short answers about matching, notifications and data sources.
All questions and the user guideIt compares vendor, product and version information with your inventory, separating exact or high-confidence matches from records requiring review. Records with missing version information need further assessment.
Malicious and suspicious indicators from threat feeds, with their sources and statuses. Suspicious records require analyst review; a listed record does not establish that your company experienced an attack.
Add the displayed TXT record to DNS for the domain. The worker checks hourly and processes up to 20 domains per run. DNS propagation and source availability can affect verification time.
Choose critical, high, medium and low levels for team notifications. Service and data breach notifications are configured separately.
CycloneDX JSON and XML, and SPDX JSON and tag-value formats are supported. Upload files in the panel or send them from CI using a company-scoped import key.
Public status sources from supported providers. A separately configured Microsoft Graph connection supports company-specific Microsoft 365 status. Provider status does not guarantee that every internal workflow is working.
Request a demonstration to discuss your organisation's needs.