Winfunc vs Assetnote
Compare external exposure visibility with code-level investigation; they address different program gaps.
Published · Matrix sources reviewed
At a glance
Pilot scorecard (PDF)Product scope follows linked public materials. Confirm availability and terms for your environment. Swipe or scroll horizontally to compare.
| Consideration | Searchlight Exposure | Winfunc |
|---|---|---|
| Scope | Searchlight Exposure, formerly Assetnote, discovers and validates external attack surface exposures.[1] | Codebase audits, diff-scoped PR review, focused security questions, and contextual triage.Details |
| Evidence & workflow | Discovered assets and validated exposures support external risk decisions; map each to an application owner.[1] | Revision-bound code paths, assumptions, and validation evidence where testing is feasible and authorized.Details |
| Remediation | Findings route to remediation workflows and exposures can be retested after a fix.[1] | Suggested patches for engineering review, explicit fix verification, and regression checks within the agreed scope.Details |
| Deployment & data | Agree authorized discovery and validation boundaries, asset attribution, data retention, and deployment terms. | Confirm source access, deployment, retention, processing region, and test boundaries in written terms. |
| Buying considerations | Confirm asset coverage, validation scope, integrations, and any separate Searchlight products. | Agree repositories, review scope, usage, required integrations, and enterprise controls in the proposal. |
Published by Winfunc. These are scope summaries and evaluation recommendations; a feature list does not establish detection quality or a winner.
Official sources and product context
Original product context reviewed
Assetnote / Searchlight Exposure: Assetnote is now Searchlight Exposure. Searchlight Cyber describes it as an external attack surface platform that continuously discovers and validates organizational exposures. Its public overview distinguishes Searchlight Exposure from Searchlight Threat, which monitors clear, deep, and dark web sources for targeting information.
Winfunc: Winfunc reviews application code, investigates security hypotheses, triages findings using application context, and prepares suggested fixes for engineering review. Its threat modeling, supply-chain review, cloud posture, and reporting workflows support the application owner’s risk and remediation decisions.
When to choose each
- Evaluate Searchlight Exposure
- You need discovery and validation of your externally visible estate.
- Evaluate Winfunc
- You need to understand risk within application code and get a reviewable fix to engineering.
- Consider both
- Connect external signals to the repository owner and agree closure evidence at both layers.
Questions for the pilot
Discovery boundary
If the concern is unknown internet-facing assets, evaluate external discovery and asset ownership. If the concern is a feature’s security behavior, evaluate code and application context.
Ask to see: A coverage boundary that distinguishes discovered assets, connected repositories, and excluded systems.
From exposure to application owner
An external exposure needs a responsible team and a remediation path. Check whether an observed asset can be mapped to the application, repository, and deployment that produce it.
Ask to see: An owned exposure linked to the relevant application and a tracked corrective action.
Verification at the right layer
External remediation and code remediation need different closure evidence. Define how you will confirm that the deployed exposure changed and that the underlying application fix is correct.
Ask to see: A deployment or configuration record, an updated review, and a documented closure decision.
Run a fair pilot.
Use the same revision and scope. Record unique findings, reviewer effort, a reviewed fix, and the limits of verification.
Free PDF. No email required.
Product-specific pilot steps
- 01List the program questions that require external asset discovery and those that require code access.
- 02Choose an authorized application with known deployment and repository ownership.
- 03Trace a relevant signal to a remediation owner and agree on closure evidence at each layer.
- 04Assess each product against its intended scope and confirm enterprise and commercial terms.