dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fixed typo in security concept doc (#2374) 

Signed-off-by: moreyhat <moreyhat@gmail.com>

Co-authored-by: Yaron Schneider <schneider.yaron@live.com>
This commit is contained in:
moreyhat 2022-04-15 17:44:41 -07:00 committed by GitHub
parent 89eb035461
commit 381ede8146
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
daprdocs/content/en/concepts/security-concept.md
View File

@ -138,7 +138,7 @@ By default Dapr doesn't transform the state data from applications. This means D
However application state often needs to get encrypted at rest to provide stronger security in enterprise workloads or regulated environments and Dapr does provide automatic client side state encryption based on AES256. Read [How-To: Encrypt application state]({{< ref howto-encrypt-state.md >}}) for more details.
## Dapr Runtrime state
## Dapr Runtime state
Importantly the Dapr runtime does not store any data at rest, meaning that Dapr runtime has no dependency on any state stores for its operation and can be considered stateless.
# Using security capabilies in an example application