{"id":130,"date":"2021-03-05T14:05:55","date_gmt":"2021-03-05T14:05:55","guid":{"rendered":"https:\/\/iamtec.eu\/en\/?page_id=130"},"modified":"2021-04-23T23:39:25","modified_gmt":"2021-04-23T21:39:25","slug":"security","status":"publish","type":"page","link":"https:\/\/iamtec.eu\/en\/security\/","title":{"rendered":"Security of Identities and\/or Systems"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"Security\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

For the security of both identities and systems, we use both the “defense” approach and the “attack” approach. From a defense perspective, both identities and systems must be secured as best as possible. With this a healthy balance between “security” and “user experience” is achieved. We do not want (too) strict security that results in a bad user experience. Bad user experience in turn will result in poor security due to incorrect behavior. To prevent that additional guidance or tooling is needed. Nevertheless, sometimes you really need to bite the bullet if you are behind on (new) security standards. Subsequently, both identities and systems must be approached from an attack perspective. The main reason for this is to learn which weaknesses still exist in order to (be able to) take measures. Those measures further mitigate risks and where possible even eliminate them completely.<\/p>

Ask yourself the following question: “why not use the knowledge of possible weaknesses yourself to make improvements, instead of having a malicious person use it against you?<\/i>“<\/p>

Ultimately, it’s all about ensuring:<\/p>