Skip to content

Documentation

VULT SECURITY DOCUMENTATION

Find the right section

Comparison methodology

Read the comparison precisely

Field guide

StatusMeaningInterpretation
YesDocumented availability within the reviewed product scope.Does not mean mandatory by default, universally deployed, independently tested or equal performance.
OptionalExplicit configuration or retention option.The customer must select and verify the intended configuration.
PartnerDelivered through a documented partner or external provider.Assess the combined offering and contract; this is not an absence of capability.
RelatedA relevant mechanism is documented, but the exact field definition is not established.Read the provider note. This is not a claim that the mechanism is weak or easily bypassed.
Not verifiedThe reviewed material does not establish the specific capability.An evidence gap, not a Yes or No. Apply the same standard to every provider; unknowns are not scored as wins or losses.
Outside scopeNot included as a native or standard capability in the reviewed offering.VULT Security: F38 is not bundled; registry checks are à la carte. F39 uses enterprise-provided transaction monitoring. The grid states these boundaries directly.
Yes (Gov)Available à la carte through VULT Sovereign for selected government customers.VULT Enterprise serves banks and businesses. VULT Sovereign services are separate; VULT Security determines government eligibility and offering scope.
ReportedThe provider states the assurance or testing status in reviewed material.Underlying report/certificate scope and freshness have not been independently inspected. The same rule applies to all providers.
BAA-ready / HIPAA statedBAA readiness is documented, or a provider states HIPAA safeguards/compliance.Distinguish the two labels. A BAA and the applicable service obligations require agreement; no HHS certification is implied.
Component testedThe supplied material describes a tested component in the integrated stack.Identify the lab, component/version and tested capture paths; do not represent it as a certification of the whole platform.
Mobile only / Hardware-dependentThe capability depends on the documented SDK, device or capture hardware.Browser and mobile SDK controls are not assumed identical.
On requestThe provider offers relevant security documents subject to its access process.Access conditions and report coverage should be confirmed.
Scope to confirmA dated, ambiguous or incomplete statement does not establish current scope.For example, a page referencing an older ISO edition needs a current certificate.

Reviewed evidence and source boundaries

Sources support only their stated scope. Company-confirmed scope; sourced competitor comparisons.