For the complete documentation index, see llms.txt. This page is also available as Markdown.

31+ Days

All Material deployments (regardless of whether you have purchased our Essentials or Advanced plans) share a number of deploy steps. Advanced packages have a few extra steps, noted as "Advanced Only."

If you're not sure which package you're deploying, Essentials or Advanced, contact Material Support.

If you bought ATO (Account Takeover) Resilience only, skip to Deploy Account Takeover Resilience.

Essential and Advanced Packages are deployed in stages, by capability. You can configure and deploy all these in one sitting, or break it up in a few sessions (see the sample rollout timelines in the Communication Template scenarios).

Detections work as soon as you're finished with the Pre-Requisites guide. However, responses, remediation, and protections may not be enabled until you complete the guides in this section.

How Material Works

At a high level, Material's workflow is broken into three areas that are referenced frequently in these Deployment Guides:

Detect

A detection is a single rule designed to identify important events or conditions within your Google Workspace or Microsoft 365 environment, which are then surfaced as Issues. At the point in deployment when you are reading this guide, detections are already enabled and working for you.

Investigate

An issue represents a single threat identified by a detection. Issues are created when detection logic matches an entity in your Google Workspace or Microsoft 365 environment. Using the evidence Material provides, you can make a decision on how to respond.

Response

Responses and remediations are the actions you can prescribe or take in Material to respond to and stop any detected threats. There are two ways to fix an issue directly in Material. Depending on the detection type, you can either set a default response, manually set a response, or apply a combination of both responses and remediations.

Last updated

Was this helpful?