Security information you can act on.
Find the product’s published security information, learn how to verify an official release, and see where a suspected vulnerability will be reported once the disclosure route is published.
Verify what you install.
Use the official download destination and the verification information for that release. When the publisher or file does not match the published details, do not install it; the disclosure route below is not yet published.
Understand the product boundary.
Read the data-flow and privacy information for the configuration you use. Local memory, cloud assistance, licensing, and connected services have different roles.
Report a concern privately.
Describe the affected component, steps needed to reproduce the concern, and the potential impact. Avoid including unrelated customer data or secrets.
Not yet published. The verified disclosure route publishes here when it exists; do not send secrets through any public channel.