Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

site updates #211

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file modified src/documentgenerator/Assets/ZeroTrustTemplate.xlsx
Binary file not shown.
33 changes: 32 additions & 1 deletion src/react/docs/app-permissions.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,11 +2,42 @@
sidebar_position: 2
---

# App Permissions
# Zero Trust Assessment Tool

## What is the Zero Trust Assessment Tool?

This PowerShaell cmdlet tool provides essential checks to confirm a strong security baseline, preparing you for advanced features and a more resilient security posture.

## How do I access it?

It is a PowerShell cmdlet. You can access it from your PowerShell command line by invoking:

```PowerShell
Install-Module ZeroTrustAssessment
Invoke-ZTAssessment
```


## How does this app work?

This app uses Microsoft Graph to read the tenant configuration and provide recommendations on improving the end to end security configuration.
When you run the cmdlet, you will be prompted to log in to your Entra ID tenant.
It is recommended to use a non-guest account for logging in. For example, if your tenant domain name is contoso.onmicrosoft.com, you should log in with an account similar to `<signin-name>@contoso.onmicrosoft.com`.

## What options are available with this tool?

You can specify an option whether to collect telemetry on the usage of this cmdlet. The only telemetry that is collected is the Entra ID tenant id (GUID) that the cmdlet is being run against. No other personal or tenant information is collected.

The switch available is `-EnableTelemetry` and it defaults to `$true`. The two values for this switch are:

- `$true`, which is the default value, indicates that the Entra ID tenant ID (GUID) will be collected
- `$false`, indicates that the Entra ID tenant ID (GUID) will NOT be collected

An example of running the cmdlet with telemetry enabled is:

```PowerShell
Invoke-ZTAssessment -EnableTelemetry $true
```

## What are the permissions required for this app?

Expand Down
11 changes: 11 additions & 0 deletions src/react/docs/videos/Assessment.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
---
sidebar_position: 5
---

# Zero Trust Assessment

Learn how to run the Zero Trust Assessment Powershell script and interpret the output.

<iframe width="560" height="315" src="https://www.youtube.com/embed/oyG3EcFd-_E?si=Vn_1qR6hnUQtnKmT" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

Learn more: https://msft.it/6050m0jfg
13 changes: 13 additions & 0 deletions src/react/docs/videos/DataPillar.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
sidebar_position: 4
---

# Data Pillar

This video covers how to deliver the data portion of the Microsoft Zero Trust Strategy Workshop.

<iframe width="560" height="315" src="
https://www.youtube.com/embed/jxKrzAQ-u_0?si=M2OshZZzA5-6P39R
" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

Learn more: https://msft.it/6057mfg2W
12 changes: 12 additions & 0 deletions src/react/docs/videos/DevicesPillar.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
---
sidebar_position: 3
---

# Devices Pillar

Welcome! This video introduces Zero Trust and the Microsoft Zero Trust Workshop

<iframe width="560" height="315" src="
https://www.youtube.com/embed/wraJn-jGd_M?si=AKBKorPL0auEXFmy
" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

13 changes: 13 additions & 0 deletions src/react/docs/videos/IdentityPillar.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
sidebar_position: 2
---

# Identity Pillar

This video covers how to deliver the Identity pillar of the Microsoft Zero Trust Strategy Workshop.

<iframe width="560" height="315" src="
https://www.youtube.com/embed/PUovOhNzY58?si=r0LEbQHfTn3ZGlWg
" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

Learn more: https://msft.it/6053mfghB
13 changes: 13 additions & 0 deletions src/react/docs/videos/IntroductionToZT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
sidebar_position: 1
---

# Introduction to the Zero Trust Workshop

This video provides an introduction to the Zero Trust Strategy Workshops, highlighting what they are and how they can help your organization develop a secure Zero Trust posture.

<iframe width="560" height="315" src="
https://www.youtube.com/embed/0-IYLWMHxGg?si=JyV0MuwIUBDKoFpN
" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

Learn more: https://msft.it/6055mfgAT
17 changes: 17 additions & 0 deletions src/react/docs/videos/index.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
import DocCardList from '@theme/DocCardList';

# Workshop Guided Videos

## Video Index

We have produced the following videos to help you run your own workshops

Introduction to the Zero Trust Workshop

Identity Pillar

Devices Pillar

Data Pillar

Zero Trust Assessment Overview
38 changes: 38 additions & 0 deletions src/react/docs/workshop-guidance/cobrandingguide.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# Workshop Cobranding Guide

## Overview
This guide provides you with instructions on how to properly co-brand the Microsoft Zero Trust Workshop workbook.

## Updating Logos
The Zero Trust Workshop Excel file provides a place for you to co-brand the workbook with your organization's logo. Replace the Contoso name and logo with your own on the "Home" tab. Ensure your logo has sufficient color contrast with the background. Be sure you follow any brand guidelines for minimum clear space or minimum size of your logo.

Do not remove, replace, move, or alter the Microsoft logo in the workbook in any way.

### To change your logo
Select the Contoso logo and select **Picture Format** in the ribbon. Click **Change Picture > This Device** and select an image file of your logo. Use a PNG or SVG file whenever possible, as these file formats support transparency.

![image](https://github.com/user-attachments/assets/8a2bb71e-6a45-4a10-8bca-6efe4f2db922)

With your newly added logo selected, click **Picture Format > Picture Border** and select **No Outline**. This will remove the magenta border.

![image](https://github.com/user-attachments/assets/e10ecfa9-88f4-4193-b888-975c12e1e47f)

Click **Picture Format > Alt Text** in the ribbon and replace "Contoso" with your organization's name.


## Accessibility
Excel includes built-in resources to help you make sure your workbooks are accessible to all. Follow these additional guidelines to ensure the final workbook is accessible and does not disclose personal information.

[Visit this Microsoft Support page to learn more about accessibility in Excel](https://support.microsoft.com/en-us/office/accessibility-best-practices-with-excel-spreadsheets-6cc05fc5-1314-48b5-8eb3-683e49b3e593)

### Privacy and Global Use Checklist
- [ ] Ensure sufficient contrast between color combinations, especially text and backgrounds. Do not put patterns or images behind text."
- [ ] Resolve any errors or warnings flagged in the built-in Accessibility Checker before saving.
- [ ] Include alt text for any non-decorative images.
- [ ] Use multiple cues, such as color and text, to convey information rather than color alone.
- [ ] Be aware of global audiences—many readers won't understand colloquial phrases or culture-specific references, and they may not understand the same visual metaphors.
- [ ] Use familiar worldwide images and a diverse set of people and places in examples.
- [ ] Use a worldwide format for dates (Month, DD YYYY) and start calendars on Mondays.
- [ ] Don't include trademark bugs for Microsoft products.
- [ ] Don't use Microsoft product names possessively (Word's) or abbreviate them.
- [ ] Make sure you have permission or license to use any quotation, photo, or image. Cite any copyrighted information.
53 changes: 53 additions & 0 deletions src/react/docs/workshop-guidance/delivery-guide.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
# Workshop Delivery Guide

## Overview
The Zero Trust Workshop helps customers to develop an actionable and orderly strategy for implementing a secure Zero Trust posture. There are two parts to the Zero Trust Workshop. The first is assessing the customer's current environment with programmatic checks that will help to identify gaps and areas for improvement. The second is helping the customer to identify projects and initiatives that they need to implement to further advance their adoption of capabilities to transform their environment.
There are currently three different workshops available for the following pillars:
- Identity
- Devices
- Data

Customers can choose to schedule all the workshops or just a subset of them depending on their priorities and resource availability. While the workshops are modular, customers are encouraged to start with Identity first, then Devices, followed by Data (and any future modules as they become available).

## Purpose
This document is for use by the delivery expert that plans on delivering the Zero Trust Pillar Workshops to customers. It aims to provide delivery experts with a comprehensive overview of the tasks that will be required to successfully deliver the Zero Trust Pillar Workshops to customers. It is structured chronologically following the standard and typical flow of a workshop delivery.

## Target Customer
The ideal customer for this engagement:
1. Understands and aligns to the Microsoft Zero Trust security vision. The Zero Trust Fundamentals Assessment is a great prerequisite to drive this alignment prior to these pillar-focused workshops.
2. Has the intent and resources to invest in projects to deploy Microsoft Security products

## Alignment with internal and external Microsoft recommendations
Although the content of the Zero Trust Workshop will be continuously updated in a quarterly cadence, most of the recommendations discovered as part of the engagement are aligned with the Zero Trust Security Deployment Guidance:
- [Zero Trust Guidance Center | Microsoft Learn](https://learn.microsoft.com/en-us/security/zero-trust/)
- [Zero Trust deployment for technology pillars overview | Microsoft Learn](https://learn.microsoft.com/en-us/security/zero-trust/deploy/overview)

## Customer Stakeholders
In order to get the most out of these workshops, it is recommended to have people on the call from the customer’s side that can cover the following areas:
- Identity and Access Management (IAM)
- Security (Governance/CERT/SOC)
- Devices/Endpoint
- App Dev
- Networking

Recommendations for the customer stakeholders that should attend each of the pillar workshops are as follows:

|Identity|Devices|Data|
|---|---|---|
| • Identity and Access Management (IAM) team <br/> • Security Operations team <br/> • Devices/Endpoint team <br/> • Enterprise Application Developers <br/> • CISO (if possible) <br/> • IT Director (if possible)| • MDM Admin (Architect, Ops) <br/> • Security (Architect, Ops) <br/> • Conditional Access Admin (Security, Identity, MDM) <br/> • Governance and Risk <br/> • CISO (if possible) <br/> • IT Director (if possible) | • Information Protection architects and officers <br/> • Compliance officers and administrators <br/> • Data Platform administrators focused on data security (Exchange, SharePoint, etc.) <br/> • CISO (if possible) <br/> • IT Director or Lead Architect (if possible)|

## Engagement Model

|Phases|Key Objectives|Key Activities|Success Criteria|
|--|--|--|--|
|**Initial Scoping call with Customer <br/> <br/> Duration: 30 minutes**| • Arrange the technical review activity and ensure scope, objectives, format and deliverables are understood by the customer <br/> • Confirm logistics and attendees <br/> • Decide which of the pillars the customer would like delivered | • Gather customer context and validate intent and readiness for Zero Trust journey <br/> • Conduct scoping meeting <br/> • Agree on the assessment logistics and schedule time to deliver individual pillar workshops <br/> • Ensure customer understands prerequisites to run the assessment checks <br/> • Vaidate required customer technical and operational stakeholders <br/> • Validate that the customer has understanding of their current Microsoft licensing arrangements for relevant services | • Workshop engagement is understood by all required stakeholders <br/> • Logistics for the review are finalized <br/> • Delivery Expert has identified way to share files with customer |
|**Assessment (optional) <br/> <br/> Duration: Depends on environment**| • Customer understands their gaps and how to optimize their already deployed services | • Customer runs the assessment checks. These might take several hours depending on the size of the environment <br/> • Delivery expert conducts a session to walk through the findings| • Customer understands findings report|
|**Roadmap Mapping (Pillar Workshop) <br/> <br/> Duration: See Workshop Delivery Time Estimates section**| • Customer has a tailored adoption roadmap to further evolve their Zero Trust posture | • If customer already took the Zero Trust Foundation Assessment, delivery expert can fill in some roadmap item statuses per their existing knowledge of customer's environment <br/> • Delivery expert leads working sessions to walk through the baseline adoption roadmap identified by Microsoft and fills it out based on customer requirements and constraints | • Csutomer has a customized deployment path with concrete deployment steps and decisions to make |
|**Closeout <br/> <br/> Duration: 1 hour**| • Gather customer feedback about the workshop <br/> • Identify additional pillar workshops to deliver | • Customer fills out feedback survey | • Workshop feedback survey is completed |

## Workshop Delivery Time Estimates
Below are the estimated delivery times for each section of the pillar workshops:
|Identity|Devices|Data|
|---|---|---|
| • Apps: 1.5 hours <br/> • Users and Groups: 1 hour <br/> • Devices: 0.5 hour <br/> • Operations: 1 hour <hr /> **• Total: 4 hours** | • Windows: 1-4 hours <br/> • Mobile Application Management (MAM): 15 - 45 minutes hour <br/> • iOS and Android MDM: 0.5-1 hour <br/> • Operations: 15 minutes <hr /> **• Total: 3-6 hours** | • Know and Protect You Data: 2 hours <br/> • Manage Data Access: 1 hour <br/> • Protect Critical Data Assets: 1 hour <hr /> **• Total: 4 hours**|

61 changes: 51 additions & 10 deletions src/react/docusaurus.config.js
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
// There are various equivalent ways to declare your Docusaurus config.
// See: https://docusaurus.io/docs/api/docusaurus-config

import {themes as prismThemes} from 'prism-react-renderer';
import { themes as prismThemes } from 'prism-react-renderer';

/** @type {import('@docusaurus/types').Config} */
const config = {
Expand Down Expand Up @@ -68,23 +68,48 @@ const config = {
// Replace with your project's social card
image: 'img/docusaurus-social-card.jpg',
navbar: {
title: 'Zero Trust Assessment',
title: 'Zero Trust Workshop',
logo: {
alt: 'Site Logo',
src: 'img/logo.svg',
},
items: [
{
type: 'docSidebar',
sidebarId: 'docsSidebar',
to: 'workshop',
position: 'left',
label: 'Docs',
label: 'About the Workshop',
},
{
type: 'docSidebar',
sidebarId: 'docsSidebar',
to: 'guide',
position: 'left',
label: 'About',
label: 'Plan',
},
{
type: 'dropdown',
position: 'left',
label: 'Learn',
items: [
{
label: "Workshop Docs",
type: 'docSidebar',
sidebarId: 'docsSidebar'
},
{
label: 'Workshop Videos',
type: 'doc',
docId: 'videos/index'
}
]
},
// {
// to: 'testimonials',
// position: 'right',
// label: 'Testimonials',
// },
{
to: 'https://aka.ms/zerotrust',
position: 'right',
label: 'Microsoft Zero Trust',
},
],
},
Expand All @@ -95,11 +120,15 @@ const config = {
title: 'Docs',
items: [
{
label: 'ZT Asssessment Checks',
label: 'Zero Trust Guidance Center',
to: 'https://learn.microsoft.com/en-us/security/zero-trust/',
},
{
label: 'Zero Trust Asssessment Checks',
to: '/docs/intro',
},
{
label: 'ZT App Permissions',
label: 'Zero Trust App Permissions',
to: '/docs/app-permissions',
},
],
Expand All @@ -124,6 +153,14 @@ const config = {
{
title: 'More',
items: [
{
label: 'Privacy',
href: 'https://go.microsoft.com/fwlink/?LinkId=521839'
},
{
label: 'Terms of Use',
href: 'https://go.microsoft.com/fwlink/?LinkID=206977'
},
{
label: 'GitHub',
href: 'https://github.com/microsoft/zerotrustassessment',
Expand All @@ -137,6 +174,10 @@ const config = {
theme: prismThemes.github,
darkTheme: prismThemes.dracula,
},
colorMode: {
defaultMode: 'light',
disableSwitch: true,
},
}),
};

Expand Down
11 changes: 10 additions & 1 deletion src/react/package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

5 changes: 3 additions & 2 deletions src/react/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,8 @@
"clsx": "^2.0.0",
"prism-react-renderer": "^2.3.0",
"react": "^18.0.0",
"react-dom": "^18.0.0"
"react-dom": "^18.0.0",
"react-icons": "^5.3.0"
},
"devDependencies": {
"@docusaurus/module-type-aliases": "^3.5.2",
Expand All @@ -44,4 +45,4 @@
"engines": {
"node": ">=18.0"
}
}
}
Loading
Loading