| 000 | 01737nam a2200313 a 4500 | ||
|---|---|---|---|
| 001 | vtls000032540 | ||
| 003 | KUKTEM | ||
| 005 | 20251117145457.0 | ||
| 008 | 081120t2008 mauda f b 001 0 eng d | ||
| 020 | _a9781596932180 | ||
| 020 | _a159693218X | ||
| 039 | 9 |
_a201107132158 _bVLOAD _c200908141652 _dVLOAD _c200908141634 _dVLOAD _c200908132131 _dVLOAD _y200811201200 _zsaini |
|
| 040 | _aUMP | ||
| 090 | _aT58.64 .C69 2008 | ||
| 100 | 1 | _aCoyne, Edward J. | |
| 245 | 1 | 0 |
_aRole engineering for enterprise security management / _cEdward J. Coyne, John M. Davis |
| 260 |
_aBoston : _bArtech House, _c2008 |
||
| 300 |
_axvii, 224 p. : _bill., charts ; _c24 cm. |
||
| 490 | 1 | _aArtech House information security and privacy series | |
| 504 | _aIncludes bibliographical references and index | ||
| 505 | 0 | _aThe business case for role-based access control -- Role engineering in the phases of the system development life cycle -- Role engineering and why we need it -- Defining good roles -- The role engineering process -- Designing the roles -- Engineering the permissions -- Tools that can be used to assist the role engineering process -- Putting it all together : the role formation process -- What others have been doing -- Planning a role engineering effort -- Staffing for role engineering -- What can go wrong and why? | |
| 650 | 0 | _aInformation resources management | |
| 650 | 0 |
_aComputer networks _xAccess control |
|
| 650 | 0 | _aComputer network architectures | |
| 650 | 0 | _aManagement information systems | |
| 700 | 1 | _aDavis, John M. | |
| 830 | 0 | _aArtech House information security and privacy series | |
| 999 |
_aVIRTUA40 _c47039 _d47045 |
||
| 999 | _aVTLSSORT0080*0200*0201*0400*0900*1000*2450*2600*3000*4900*5040*5050*6500*6501*6502*6503*7000*8300*9991 | ||