Security
WMT evaluates identity, authorization, application safeguards, infrastructure, delivery, operations, and incident handling in the context of the applicable solution.
Control areas
The exact controls and responsible party vary by product, deployment, integration, infrastructure, service, and signed agreement.
Authentication, identity sources, roles, permissions, privileged access, account lifecycle, administrative actions, and user responsibility.
Secure application behavior, validation, authorization, session handling, data access, exports, logging, integrations, and configuration.
Hosting boundary, network and platform controls, secrets, patching, monitoring, backup responsibilities, support access, and operational change.
Customer context
The customer’s identity systems, devices, networks, administrators, data handling, connected platforms, and operating procedures remain part of the risk model.
| Customer identity and users | User verification, account ownership, role approval, credential protection, timely removal, endpoint security, and acceptable use. |
|---|---|
| Customer infrastructure | Where customer-managed, network, server, operating system, database, backup, monitoring, and administrative controls remain customer responsibilities. |
| Connected systems | Identity providers, SIS/ERP platforms, email, payment, storage, analytics, and other third parties introduce their own controls and dependencies. |
| Operational procedures | Approval, segregation of duties, data export, report distribution, incident escalation, support authorization, and change governance. |
Security contact
Do not use a public form to send credentials, personal data, customer records, exploit code, or sensitive vulnerability detail.
Security file
The website security file provides the current public security-contact route and disclosure guidance.
Open security.txtExisting customer
For an existing environment, use the established support and escalation process so the affected product and customer context are known.
Contact SupportEvaluation
Route due-diligence questionnaires, architecture questions, and proposed security terms through the commercial evaluation process.
Contact SalesGeneral
Use the general contact route when the correct commercial, project, or support owner is not yet known.
Contact WMTQuestions
No. This page does not claim ISO, SOC, PCI, government, or other certification. Any certification or independent-assurance claim must be supported by a current authoritative document.
WMT products support product-appropriate identity, authentication, roles, permissions, and administrative controls. Exact capabilities, identity integrations, configuration, and customer responsibilities vary by product and deployment.
Encryption requirements and implementation depend on the product, deployment, infrastructure, interface, and agreement. They should be confirmed in the applicable technical and contractual documentation rather than assumed from a general website statement.
Secure development, dependency management, testing, release, patching, and operational responsibilities should be defined for the applicable product and service. Exact timelines and coverage require confirmation.
Use the published security contact in the site security file or the established Support channel for an existing customer. Do not include exploit details or sensitive data in a public form.
Security in context
The right answer depends on the applicable solution and relationship—not a generic control list.
