dido:public:ra:1.4_req:2_nonfunc:25_security
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:1.4_req:2_nonfunc:25_security [2021/10/09 15:26] nick |
dido:public:ra:1.4_req:2_nonfunc:25_security [2022/04/12 15:20] (current) nick |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== About ===== | ===== About ===== | ||
| + | [[[[dido:public:ra:1.4_req:2_nonfunc:25_security | Return to Top]] | ||
| + | |||
| Security is not a single "thing" that can be added to a system. To be truly secure, the entire [[dido:public:ra:xapend:xapend.a_glossary:e:e2esolution]] needs to be secure and needs to be considered during the entire [[dido:public:ra:xapend:xapend.a_glossary:s:syslifecycle]]. As shown in Figure {{ref>layerSecure}}, a layered approach is used to help isolate the security needs. Each layer represents a portion of the [[dido:public:ra:xapend:xapend.a_glossary:i:infotech]] stack, including the people who use and have access to the IT stack. | Security is not a single "thing" that can be added to a system. To be truly secure, the entire [[dido:public:ra:xapend:xapend.a_glossary:e:e2esolution]] needs to be secure and needs to be considered during the entire [[dido:public:ra:xapend:xapend.a_glossary:s:syslifecycle]]. As shown in Figure {{ref>layerSecure}}, a layered approach is used to help isolate the security needs. Each layer represents a portion of the [[dido:public:ra:xapend:xapend.a_glossary:i:infotech]] stack, including the people who use and have access to the IT stack. | ||
dido/public/ra/1.4_req/2_nonfunc/25_security.1633807572.txt.gz · Last modified: 2021/10/09 15:26 by nick
