richardk/iso27diy-corp
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

removed emoji's in folders and links

Browse source
This commit is contained in:
Richard Kranendonk 2026-05-11 16:02:08 +02:00
parent 6992777c0e
commit 9b7b3a3a85
88 changed files with 1476 additions and 104 deletions
Download patch file Download diff file Expand all files Collapse all files

2
Corpus/Literature notes/Single Sign On (SSO).md
View file

@ -20,7 +20,7 @@ For both users and IT administrators, securely handling thousands of accounts an
## SSO’s challenges
- **Extra-strong passwords must be enforced.** If an SSO account is cracked, others under the same authentication can also be endangered. -> combine with [Multi-factor authentication](../🎇%20Sparks/Multi-factor%20authentication.md)
- **Extra-strong passwords must be enforced.** If an SSO account is cracked, others under the same authentication can also be endangered. -> combine with [Multi-factor authentication](../Sparks/Multi-factor%20authentication.md)
- **When SSO is down, access to all connected sites is stopped.** This is a big reason to exercise great care in choosing an SSO system. It must be exceptionally reliable and plans should be in place for dealing with breakdowns.
- **What’s more, when your identity provider goes down, your SSO does too.** The provider’s vulnerability to any kind of interruption becomes your vulnerability as well, and it is probably beyond your control. Once again, the choice of vendors is critical.
- **If a hacker breaches your identity provider user account, all your linked systems could be open to attack.** This can be a classic single point of failure and should be headed off in the planning process. On the plus side, high-quality identity providers have top-notch security.