Spearhead/rfd
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fixed formatting (80 line width)

Browse Source
This commit is contained in:
Marius Pana 2018-01-05 12:18:54 +02:00
parent 2a73c7e05f
commit 0612f9edeb
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
rfd/0001/README.md
View File

@ -23,7 +23,8 @@ as well.
## Key Requirements
We wish to have a central location for all user authentication requests so that
we can easily create and manage users. We can then use this central store to authenticate with all of our required services.
we can easily create and manage users. We can then use this central store to
authenticate with all of our required services.
The first principles we are looking at include:
@ -52,5 +53,11 @@ configuration files (possibly other details) for the framework.
## What is the security impact?
A compromised directory could allow an attacker access to sensitive information or services. Furthermore a compromised directory could be used against us and therefore other methods of access for critical situations must be implemented (local accounts, override mechanisms, etc.). A mechanism to disable/invalidate all accounts must be implemented.
A compromised user account impact depends on the privileges of the compromised account. A mechanism to quickly disable any compromised account must be implemented.
A compromised directory could allow an attacker access to sensitive information
or services. Furthermore a compromised directory could be used against us and
therefore other methods of access for critical situations must be implemented
(local accounts, override mechanisms, etc.). A mechanism to disable/invalidate
all accounts must be implemented.
A compromised user account impact depends on the privileges of the compromised
account. A mechanism to quickly disable any compromised account must be
implemented.