| 000 | 01995nam a22003734a 4500 | ||
|---|---|---|---|
| 001 | ebr10240780 | ||
| 003 | CaPaEBR | ||
| 006 | m u | ||
| 007 | cr cn||||||||| | ||
| 008 | 080229s2008 mauad sb 001 0 eng | ||
| 010 | _z 2008270416 | ||
| 020 | _z9781596932180 | ||
| 020 | _z159693218X | ||
| 040 |
_aCaPaEBR _cCaPaEBR |
||
| 035 | _a(OCoLC)560506562 | ||
| 050 | 1 | 4 |
_aT58.64 _b.C69 2008eb |
| 100 | 1 |
_aCoyne, Edward J., _cPhD. |
|
| 245 | 1 | 0 |
_aRole engineering for enterprise security management _h[electronic resource] / _cEdward J. Coyne, John M. Davis. |
| 260 |
_aBoston : _bArtech House, _c2008. |
||
| 300 |
_axvii, 224 p. : _bill., charts. |
||
| 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? | |
| 533 |
_aElectronic reproduction. _bPalo Alto, Calif. : _cebrary, _d2013. _nAvailable via World Wide Web. _nAccess may be limited to ebrary affiliated libraries. |
||
| 650 | 0 | _aInformation resources management. | |
| 650 | 0 |
_aComputer networks _xAccess control. |
|
| 650 | 0 | _aComputer network architectures. | |
| 650 | 0 | _aManagement information systems. | |
| 655 | 7 |
_aElectronic books. _2local |
|
| 700 | 1 | _aDavis, John M. | |
| 710 | 2 | _aebrary, Inc. | |
| 830 | 0 | _aArtech House information security and privacy series. | |
| 856 | 4 | 0 |
_uhttp://site.ebrary.com/lib/rucke/Doc?id=10240780 _zAn electronic book accessible through the World Wide Web; click to view |
| 999 |
_c36011 _d36011 |
||