An AWS data champion!
| https://twitter.com/disintegr8te/ | |
| Github | https://github.com/disintegr8te |
| [email protected] | |
| Twittodon | https://twittodon.com/share.php?t=disintegr8te&[email protected] |

| https://twitter.com/disintegr8te/ | |
| Github | https://github.com/disintegr8te |
| [email protected] | |
| Twittodon | https://twittodon.com/share.php?t=disintegr8te&[email protected] |
@kadin @jacob I would agree on the Assume Breach Part.
But LastPass made major Design Mistakes:
URL‘s in the Vault not encrypted. (Thinkmof Tokens, API Keys etc., they knew for 6 Years)
Master Password is used for Encryption which is fundamental different to for as Example 1Password with their Secret Key and Password Approach.
Using PBKDF2-SHA256 with 100100 rounds which is not up to date.
Also there Communication looks not really fully transparent.
An AWS data champion!
I just wrote a post about the current state of growth in infosec.exchange at the one month mark post E-day here: https://blog.infosec.exchange/2022/11/27/an-update-on-growth-of-infosec-exchange/
Note: I installed a plugin that will allow you to follow blog posts there by following @[email protected]