Win32 app isolation is a new security feature on Windows that helps contain the damage and safeguard user privacy choices in the event of an
3
+
application compromise.
4
+
Win32 app isolation is built on the foundation of [AppContainers](https://learn.microsoft.com/en-us/windows/win32/secauthz/implementing-an-appcontainer), which offer a security boundary,
5
+
and components that virtualize resources and provide brokered access to other resources.
6
+
This repo contains the documentation and tools to help you isolate your applications.
2
7
3
-
- Developer tools and documentation to help package win32 applications.
8
+
## Getting started
9
+
* The first step to isolating your application is to package it to run isolated by following the instructions [here](docs/packaging/msix-packaging-tool.md).
10
+
* Once you have your application packaged, use [Application Capability Profiler](docs/profiler/application-capability-profiler.md) to update the application to grant it access to additional resources.
11
+
* We also have additional documentation about the [fundamentals](docs/fundamentals) including file access consent.
12
+
* You're now ready to deploy and run your application on Windows.
13
+
14
+
Binaries for the tools used to package applications to run isolated are shared under the [releases](../../releases) section of the repo.
15
+
16
+
Release notes for supported Windows builds and tools can be found [here](relnotes/RELEASE_NOTES.md).
17
+
18
+
## Communicating with the team
19
+
We'd love to hear your feedback and answer your questions!
20
+
The best way to communicate with the team is through GitHub [discussions](../../discussions) and [issues](../../issues).
21
+
Please search for similar discussions and issues before creating new ones.
22
+
23
+
## Resources
24
+
You can find additional information about Win32 app isolation using the following resources:
Dylan DSilva
committed
with
GitHub
11 months ago
1 parent a108f841