Info
- Utilizzare la checkbox di selezione a fianco di ciascun documento per attivare le funzionalità di stampa, invio email, download nei formati disponibili del (i) record.
Deployment guide series : IBM Tivoli Security Compliance Manager / / Axel Buecker, Hendrik H. Fulda, Dieter Riexinger
| Deployment guide series : IBM Tivoli Security Compliance Manager / / Axel Buecker, Hendrik H. Fulda, Dieter Riexinger |
| Autore | Bucker Axel |
| Edizione | [1st ed.] |
| Pubbl/distr/stampa | Austin, TX, : IBM International Technical Support Organization, 2005 |
| Descrizione fisica | xii, 196 p |
| Disciplina | 005.8 |
| Altri autori (Persone) |
FuldaHendrik H
RiexingerDieter |
| Collana | Redbooks |
| Soggetto topico |
Electronic commerce - Security measures
Business enterprises - Computer networks - Access control Computer networks - Access control |
| Formato | Materiale a stampa  |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Front cover -- Contents -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Part 1 Architecture and design -- Chapter 1. Business context for security compliance management -- 1.1 Introduction to compliance management -- 1.2 Why compliance management? -- 1.3 Determining the how: influencing factors -- 1.4 General challenges -- 1.5 Conclusion -- Chapter 2. Tivoli Security Compliance Manager design and structure -- 2.1 Logical component architecture -- 2.1.1 Data collection components -- 2.1.2 Compliance evaluation components -- 2.1.3 Compliance report components -- 2.1.4 Security Compliance Manager server -- 2.1.5 Administration components -- 2.2 Physical component architecture -- 2.2.1 Communication port usage -- 2.2.2 Deployment on physical nodes -- 2.3 Security Compliance Manager walkthrough -- Chapter 3. Architecting a Security Compliance Management solution -- 3.1 Solution architectures, design, and methodologies -- 3.2 Design process -- 3.2.1 Typical context of Security Compliance Manager solutions -- 3.2.2 Phased project approach -- 3.2.3 Placing components in network zones -- 3.2.4 Deployment of Security Compliance Manager clients -- 3.2.5 Delegated administration -- 3.2.6 Implementation of Security Compliance Manager policies -- 3.2.7 Integration with access control management systems -- 3.2.8 Integration with Tivoli Risk Manager -- 3.3 Business processes and compliance management -- 3.3.1 A generic security compliance management business process -- 3.3.2 Security Compliance Manager business process support -- 3.3.3 Automated security compliance management -- Part 2 Customer environment -- Chapter 4. Armando Brothers Banking Corp. -- 4.1 Company profile -- 4.2 Current IT architecture -- 4.2.1 Existing security infrastructure -- 4.2.2 Existing middleware infrastructure.
4.3 Current security policies and standards -- 4.4 Emerging problems -- 4.5 Strategic objectives -- 4.6 Critical success factors for strategy implementation -- 4.7 Resulting business requirements -- 4.8 Requirements on project execution -- 4.9 ROI study and results -- Chapter 5. Security Compliance Manager design -- 5.1 Functional requirements -- 5.1.1 Phase I: Establishing a baseline -- 5.1.2 Phase II: Extend coverage -- 5.2 Design objectives -- 5.2.1 General and infrastructure objectives -- 5.2.2 Platform specific security concepts -- 5.3 Implementation architecture -- 5.3.1 Physical components -- 5.3.2 User roles and responsibilities -- 5.4 Project organization -- Chapter 6. Technical implementation -- 6.1 Deployment phase I -- 6.1.1 Planning and installing the server -- 6.1.2 DB2 maintenance tasks -- 6.1.3 Deploying clients -- 6.1.4 Installing the reporting server -- 6.1.5 Configuring operational reports -- 6.2 Deployment phase II -- 6.2.1 Tivoli Access Manager integration -- 6.2.2 Tivoli Risk Manager integration -- 6.2.3 Collector development -- 6.2.4 Report development -- 6.3 Conclusion -- Part 3 Appendixes -- Appendix A. Developing a custom collector -- Required method getReleaseNumber() -- Required method getCompatibleOS() -- Required method getDescription() -- Required method getParameters() -- Required method getTables() -- Required method executeV2() -- Appendix B. Introducing the Security Vulnerability Index -- So what is the IBM Global Services Vulnerability Index? -- How does it work? -- Appendix C. Additional material -- Locating the Web material -- Using the Web material -- How to use the Web material -- Glossary -- Related publications -- IBM Redbooks -- Other publications -- Online resources -- How to get IBM Redbooks -- Help from IBM -- Index -- Back cover. |
| Record Nr. | UNINA-9910815714003321 |
Bucker Axel
|
||
| Austin, TX, : IBM International Technical Support Organization, 2005 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Enterprise business portals II with IBM tivoli access manager / / Axel Bucker et al
| Enterprise business portals II with IBM tivoli access manager / / Axel Bucker et al |
| Autore | Bucker Axel |
| Pubbl/distr/stampa | San Jose, CA, : IBM, 2003 |
| Descrizione fisica | xxii, 468 p. : ill |
| Disciplina | 658.4/72 |
| Altri autori (Persone) |
AntoniusJesper
RiexingerDieter SommerFrank SumidaAtsushi |
| Collana | IBM redbooks |
| Soggetto topico |
Computer networks - Security measures
Web portals - Security measures |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Front cover -- Contents -- Figures -- Tables -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Part 1 Integration design and architecture -- Chapter 1. IBM WebSphere Portal integration -- 1.1 WebSphere Portal offerings -- 1.1.1 WebSphere Portal Enable -- 1.1.2 WebSphere Portal Extend -- 1.1.3 WebSphere Portal Experience -- 1.2 WebSphere Portal architecture -- 1.2.1 Presentation services -- 1.2.2 WebSphere Portal infrastructure -- 1.2.3 Tivoli Access Manager integration architecture -- 1.3 WebSphere Portal security -- 1.3.1 Authentication -- 1.3.2 Authorization -- 1.3.3 Administration -- 1.4 WebSphere Portal and Tivoli Access Manager -- 1.4.1 Tivoli Access Manager added value -- 1.4.2 Tivoli Access Manager managing WebSphere Portal resources -- Chapter 2. SAP Workplace and SAP Enterprise Portal integration -- 2.1 mySAP.com portfolio -- 2.1.1 mySAP.com Workplace -- 2.1.2 SAP Enterprise Portal -- 2.2 mySAP.com Workplace -- 2.2.1 SAP Workplace architecture -- 2.2.2 SAP Workplace security -- 2.3 SAP Workplace using Tivoli Access Manager -- 2.3.1 Access Manager added value -- 2.3.2 Access Manager integration architecture -- 2.4 SAP Portal -- 2.4.1 Introduction -- 2.4.2 SAP Enterprise Information Portal architecture -- 2.4.3 SAP Enterprise Portal security -- 2.5 SAP Portal security using Tivoli Access Manager -- 2.5.1 Access Manager added value -- 2.5.2 Access Manager integration architecture -- Chapter 3. Web Services integration -- 3.1 General business environment -- 3.2 Web Services definition -- 3.2.1 Web Services model -- 3.3 Web Services for real business -- 3.3.1 Security overview -- 3.3.2 XKMS overview -- 3.3.3 SAML overview -- 3.3.4 Summary -- 3.4 Security integration with Tivoli Access Manager -- 3.4.1 Introduction -- 3.4.2 Security models.
3.4.3 Administration of Web Services with aznAPI -- 3.4.4 Configuration of Web Services with Tivoli Access Manager -- Part 2 Automobile industry solution -- Chapter 4. Automobile industry solution -- 4.1 Group structure and company profile -- 4.2 Current architecture -- 4.3 Corporate business vision and objectives -- 4.4 Project layout and implementation phases -- 4.5 Business requirements -- 4.6 Functional requirements -- 4.6.1 Risk assessment -- 4.7 Security design objectives -- 4.8 Design approach -- 4.9 Implementation architecture -- 4.9.1 Single sign-on architecture -- 4.9.2 Infrastructure -- 4.9.3 Authorization architecture -- 4.10 Technical implementation -- 4.10.1 Implementing the portal platform -- 4.10.2 SAP ITS integration -- 4.10.3 Exchange 2000 integration -- 4.10.4 Lotus QuickPlace integration -- 4.10.5 Integrating Business Intelligence -- 4.10.6 Performing risk assessment -- 4.11 Conclusion -- Part 3 Retail industry solution -- Chapter 5. Retailer industry solution -- 5.1 Company structure and profile -- 5.2 Current architecture -- 5.3 Corporate business vision and objectives -- 5.4 Project layout and implementation -- 5.5 Business requirements -- 5.6 Functional requirements -- 5.6.1 Risk assessment -- 5.7 Security design objectives -- 5.8 Implementation architecture -- 5.8.1 Integration of Tivoli Access Manager into the architecture -- 5.8.2 Integration of WebSphere Portal into the architecture -- 5.9 Technical implementation -- 5.9.1 System setup -- 5.9.2 Configure Tivoli Access Manager -- 5.9.3 Configure WebSphere Portal Version 4.1.4 -- 5.9.4 Configuring WebSphere Portal to use Tivoli Access Manager -- 5.9.5 Configuring WebSEAL single sign-on -- 5.10 Conclusion -- Chapter 6. Federated single sign-on -- 6.1 Business requirements -- 6.2 Functional requirements -- 6.2.1 Risk assessment -- 6.3 Security design objectives. 6.4 Design approach -- 6.5 Implementation architecture -- 6.6 Technical implementation -- 6.6.1 Precondition -- 6.6.2 Sample Custom SOAP rpc Servlet -- 6.7 Conclusion -- Part 4 Appendixes -- Appendix A. mySAP Workplace integration guide -- Overview -- Version information -- Configuration -- WebSEAL configuration -- mySAP Workplace configuration -- Management issues -- User administration -- Appendix B. mySAP Enterprise Portal integration guide -- Overview -- Integration product version information -- Scenario 1 -- Configure WebSEAL -- Configure SAP Enterprise Portal -- Scenario 2 -- Configure WebSEAL -- Configure mySAP Enterprise Portal -- Other integration considerations -- Configuring network firewalls -- Known problems -- Tivoli Access Manager global sign-On (GSO) -- Creating a Tivoli Access Manager GSO resource -- Creating the WebSEAL GSO junction -- Creating and modifying WebSEAL users -- Creating a resource credential -- Configure back-end Web server for BA authentication -- GSO administration and management considerations -- Initial GSO credential population -- Multiple point of access -- GSO password management and synchronization -- Password synchronization between the same registry -- Password synchronization between Access Manager and NT domains -- Appendix C. Solaris installation guidelines -- Verify the current Solaris configuration -- DB2 Version 7.2 installation -- DB2 installation verification -- WebSphere Application Server installation -- WebSphere Application Server installation verification -- WebSphere Application Server security setup -- Personalization and portal installation -- WebSphere Portal verification -- Personalization Workspace verification -- Applying fixpacks -- WebSEAL configuration -- Summary of configuration files involved -- Configure WebSphere Application Server and WebSphere Portal. Configure Tivoli Access Manager -- Set up SSO between WebSEAL and HTTP Server -- Pass WebSphere Portal authorization to Access Manager -- Enable SSL between WebSEAL and HTTP Server -- Improving Portal Server performance -- Sample configuration files -- Appendix D. CGI-program for inactivity timeout -- Appendix E. Additional material -- Locating the Web material -- Using the Web material -- How to use the Web material -- Glossary -- Related publications -- IBM Redbooks -- Other resources -- Referenced Web sites -- How to get IBM Redbooks -- IBM Redbooks collections -- Index -- Back cover. |
| Record Nr. | UNINA-9910824916403321 |
|
Bucker Axel
|
||
| San Jose, CA, : IBM, 2003 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Federated identity management and web services security with IBM tivoli security solutions / / Axel Buecker et al
| Federated identity management and web services security with IBM tivoli security solutions / / Axel Buecker et al |
| Autore | Bucker Axel |
| Pubbl/distr/stampa | San Jose, CA, : IBM, International Technical Support Organization, 2005 |
| Descrizione fisica | xx, 478 p. : ill |
| Altri autori (Persone) |
FilipWerner
HintonHeather HippensteilHeinz Peter HollinMark NeucomRay WeedenShane WestmanJohan |
| Collana | Redbooks |
| Soggetto topico |
IBM software
Computer security |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Front cover -- Contents -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Part 1 Architecture and design -- Chapter 1. Business context for identity federation -- 1.1 Federated identity -- 1.2 Business environment -- 1.2.1 Deconstruction of the enterprise -- 1.2.2 Enterprise re-aggregation -- 1.2.3 High-level example of a re-aggregated business -- 1.2.4 Business models for federated identity -- 1.2.5 The relationship - Trust and assurance -- 1.3 IT environment -- 1.3.1 The role of identity management -- 1.3.2 Dealing with identities -- 1.3.3 User life cycle management -- 1.3.4 Inter-enterprise application to application integration -- 1.3.5 Open standards -- 1.4 Conclusion -- Chapter 2. Architecting an identity federation -- 2.1 Federation example -- 2.2 Federated identity management architecture -- 2.2.1 Background to federation -- 2.2.2 Architecture overview -- 2.2.3 Roles -- 2.2.4 Identity models -- 2.2.5 Identity attributes -- 2.2.6 Trust -- 2.2.7 Federation protocol -- 2.3 FIM standards and efforts -- 2.3.1 SSL/TSL -- 2.3.2 Security Assertion Markup Language (SAML) -- 2.3.3 Shibboleth -- 2.3.4 Liberty -- 2.3.5 WS-Federation -- 2.3.6 WS-Trust -- 2.3.7 WS-Security -- 2.3.8 WS-Provisioning -- 2.3.9 Selecting Federation standards -- 2.4 Federated single sign-on -- 2.4.1 Push and Pull SSO -- 2.4.2 Account linking -- 2.4.3 Where are you from (WAYF) -- 2.4.4 Session management and access rights -- 2.4.5 Logout -- 2.4.6 Credentials clean up -- 2.4.7 Global good-bye -- 2.4.8 Account de-linking -- 2.5 Web services security management -- 2.5.1 Web services -- 2.5.2 Web services security -- 2.5.3 Gateways -- 2.6 Federated identity provisioning -- 2.7 On demand security reference architecture -- 2.7.1 Policy management -- 2.7.2 Identity management -- 2.7.3 Key management.
2.7.4 Credential exchange -- 2.7.5 Identity federation -- 2.7.6 Authorization -- 2.8 On demand integration reference architecture -- 2.8.1 Connectivity services -- 2.8.2 User interaction services -- 2.8.3 Application and information assets -- 2.8.4 Business application services -- 2.8.5 Partner services -- 2.8.6 Infrastructure services -- 2.9 Method for architecting secure solution -- 2.9.1 Implementation flow -- 2.9.2 Definition phase of a federated identity management solution -- 2.10 Conclusion -- Chapter 3. Tivoli Federated Identity Manager architecture -- 3.1 Federated Identity Management functionality -- 3.2 Federation services -- 3.2.1 Point of contact (PoC) -- 3.2.2 Single sign-on protocol services (SPS) -- 3.2.3 Trust services -- 3.2.4 Key services (KESS) -- 3.2.5 Identity services -- 3.2.6 Authorization services -- 3.2.7 Provisioning services -- 3.2.8 Management Services -- 3.3 Federated single sign-on -- 3.3.1 Architecture overview -- 3.3.2 Trust in F-SSO -- 3.3.3 F-SSO protocol functionality -- 3.3.4 Integrating SSO with Access Manager for e-business -- 3.3.5 F-SSO approaches -- 3.3.6 InfoService -- 3.3.7 Specified level view of F-SSO architecture -- 3.4 Web services security management -- 3.4.1 Architecture overview -- 3.4.2 WS-Security -- 3.4.3 Web services Gateway or Firewall -- 3.4.4 WS-Trust -- 3.4.5 Authorization services (AS) -- 3.4.6 Web services security management architecture approach -- 3.5 Provisioning services -- 3.5.1 Architecture overview -- 3.5.2 Provisioning architecture approach -- 3.6 Conclusion -- Chapter 4. Deploying Tivoli Federated Identity Manager -- 4.1 Federated SSO architecture patterns -- 4.1.1 Architecture approach -- 4.1.2 Base pattern -- 4.1.3 Plug-in pattern -- 4.1.4 Lightweight Access Manager for e-business pattern -- 4.1.5 Highly available architecture patterns -- 4.1.6 Multiple data center patterns. 4.2 Federated Web services architecture patterns -- 4.2.1 Architecture approach -- 4.2.2 Point-to-point pattern -- 4.2.3 XML gateway pattern -- 4.3 Integrating applications into an F-SSO environment -- 4.3.1 Attribute flow between providers -- 4.3.2 User-controlled federated life cycle management -- 4.3.3 Customized user-managed federation management -- 4.4 Customizing F-SSO -- 4.4.1 Customizing page templates -- 4.4.2 Customizing Access Manager for e-business page templates -- 4.4.3 Storing aliases -- 4.5 Solution design considerations -- 4.5.1 Exchanging metadata with your partners -- 4.5.2 Availability of IBM Access Manager for e-business policy server -- 4.5.3 Key management -- 4.5.4 Session timeout -- 4.5.5 Application logout -- 4.6 Conclusion -- Chapter 5. Integrating with IBM identity management offerings -- 5.1 IBM Tivoli Access Manager for e-business -- 5.1.1 Identity provider integration -- 5.1.2 Service provider integration -- 5.2 IBM Tivoli Identity Manager -- 5.2.1 Identity provider integration -- 5.2.2 Service provider integration -- 5.3 IBM Tivoli Directory Integrator -- 5.3.1 Identity provider integration -- 5.3.2 Service provider integration -- 5.4 IBM Tivoli Directory Server -- 5.4.1 Identity provider integration -- 5.4.2 Service provider integration -- 5.5 IBM WebSphere Application Server -- 5.5.1 Integrated Solutions Console (ISC) -- Part 2 Customer environment -- Chapter 6. Overview -- 6.1 Use case 1 - SAML/JITP -- 6.2 Use case 2 - WS-Federation -- 6.3 Use case 3 - Liberty -- 6.4 Use case 4 - Web services security management -- 6.5 Conclusions -- Chapter 7. Use case 1 - SAML/JITP -- 7.1 Scenario details -- 7.1.1 Contract -- 7.1.2 User experience -- 7.2 Functionality -- 7.2.1 Single sign-on - SPNEGO -- 7.2.2 Single sign-on - SAML/JITP -- 7.3 Partners involved -- 7.3.1 BigCorp -- 7.3.2 RBTravel -- 7.4 Interaction description. 7.4.1 High-level Interaction overview -- 7.4.2 Single sign-on from Windows workstation (SPNEGO) -- 7.4.3 Single sign-on from BigCorp to RBTravel (SAML/JITP) -- 7.5 Configuration data -- 7.5.1 IdP-related configuration data -- 7.5.2 SP-related configuration data at RBTravel -- 7.6 Assumptions/implementation notes -- Chapter 8. Use case 2 - WS-Federation -- 8.1 Scenario details -- 8.2 Contract -- 8.3 User experience -- 8.3.1 Single sign-on user experience -- 8.3.2 Sign-off user experience -- 8.4 Functionality -- 8.4.1 Single sign-on - WS-Federation -- 8.5 Partners involved -- 8.5.1 BigCorp -- 8.5.2 RBTelco -- 8.6 Interaction description -- 8.7 Configuration data -- 8.7.1 Identity provider configuration at BigCorp -- 8.7.2 Service provider configuration at RBTelco -- 8.8 Assumptions/implementation notes -- 8.8.1 Understanding the many-to-one user identity mapping -- Chapter 9. Use case 3 - Liberty -- 9.1 Scenario details -- 9.1.1 Contract -- 9.1.2 User experience -- 9.2 Functionality -- 9.3 Partners involved -- 9.3.1 RBTelco -- 9.3.2 RBTickets -- 9.3.3 RBBanking -- 9.4 Interaction description -- 9.4.1 Liberty account federation -- 9.4.2 Single sign-on to partners (Liberty) -- 9.4.3 Single sign-off -- 9.5 Configuration data -- 9.5.1 Identity provider configuration at RBTelco -- 9.5.2 RBTickets service provider configuration data -- 9.5.3 RBBanking service provider configuration data -- 9.6 Assumptions/implementation notes -- 9.6.1 InfoService integration -- 9.6.2 Page customizations -- Chapter 10. Use case 4 - Web services security management -- 10.1 Scenario details -- 10.1.1 Contract -- 10.1.2 User experience -- 10.2 Functionality -- 10.2.1 Web services security management at RBTelco -- 10.2.2 Web services security management at RBStocks -- 10.3 Partners involved -- 10.3.1 RBTelco -- 10.3.2 RBStocks -- 10.4 Interaction description. 10.4.1 Web services security management Token Generator with Access Manager binary security token callback handler -- 10.4.2 Web services security management Token Consumer with Access Manager Credential login module -- 10.4.3 Web services security management Token Generator with Web services security management Callback handler -- 10.4.4 Web services security management Token Consumer with SAML Assertion login module -- 10.5 Configuration data -- 10.5.1 Overall architecture and prerequisites -- 10.5.2 RBTelco configuration -- 10.5.3 Outbound Web services gateway configuration -- 10.5.4 RBStocks configuration -- 10.6 Troubleshooting -- 10.6.1 Using the logs for Web services security management -- 10.6.2 Using the logs for the Secure Token Service -- 10.6.3 Using the WebSphere logs -- 10.6.4 Using TCPMON -- Part 3 Appendixes -- Appendix A. Configuring Access Manager WebSEAL and Web plug-in -- Introduction -- Identity provider integration -- Configuring WebSEAL as an identity provider -- Updating WebSEAL configuration file -- Configuring a junction to Tivoli Federated Identity Manager -- Configuring extended attributes for credentials in WebSEAL -- Configuring Web plug-ins as an identity provider -- Updating Web plug-in configuration file -- Configuring extended attributes for credentials in Web plug-ins -- Service provider integration -- External Authentication Interface -- Trigger URIs -- EAI headers -- External Authentication Interface example -- EAI header variables reference -- Configuring WebSEAL as a service provider -- Updating WebSEAL configuration file -- Configuring a junction to Tivoli Federated Identity Manager -- Access Manager policy for trigger URLs for EAI -- Sending extended attributes as HTTP headers with WebSEAL -- Configuring Web plug-ins as a service provider -- Updating Web plug-in configuration file. Access Manager policy for trigger URLs. |
| Record Nr. | UNINA-9910810924303321 |
|
Bucker Axel
|
||
| San Jose, CA, : IBM, International Technical Support Organization, 2005 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Integrated identity management using IBM Tivoli security solutions / / [Axel Bucker ... et al.]
| Integrated identity management using IBM Tivoli security solutions / / [Axel Bucker ... et al.] |
| Autore | Bucker Axel |
| Edizione | [1st ed.] |
| Pubbl/distr/stampa | Austin, TX, : IBM, International Technical Support Organization, c2004 |
| Descrizione fisica | 1 online resource (198 p.) |
| Altri autori (Persone) | BuckerAxel |
| Collana | IBM redbooks |
| Soggetto topico |
Electronic commerce - Security measures
Business enterprises - Computer networks - Security measures Computer networks - Access control |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Front cover -- Contents -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Part 1 Why Integrated Identity Management -- Chapter 1. An introduction to a new reference architecture -- 1.1 Everything is on demand today -- 1.2 Security management methods and practices -- 1.2.1 Confidentiality -- 1.2.2 Integrity -- 1.2.3 Availability -- 1.2.4 Areas of security implied in the CIA Triad -- 1.3 Business drivers -- 1.4 Issues affecting identity integration solutions -- 1.5 Integrated identity in the enterprise -- 1.5.1 Access control management -- 1.5.2 Identity and credential management -- 1.5.3 Audit management -- 1.5.4 Directory management -- 1.5.5 Privacy management -- 1.6 Conclusion -- Chapter 2. What Bank International -- 2.1 Company profile -- 2.1.1 Geographic distribution of WBI -- 2.1.2 Organization of WBI -- 2.1.3 HR and personnel procedures -- 2.2 Current IT architecture -- 2.2.1 Overview of the WBI network -- 2.2.2 Recently implemented e-business initiative -- 2.2.3 Security infrastructure deployed for the e-business initiative -- 2.2.4 Secured e-business initiative architecture -- 2.2.5 Identity management and emerging problems -- 2.3 Corporate business vision and objectives -- 2.4 Business requirements -- 2.4.1 Business requirements for phase 1 -- 2.4.2 Business requirements for phase 2 -- 2.5 Functional requirements -- 2.5.1 Phase 1 -- 2.5.2 Phase 2 -- 2.6 Risk assessment -- 2.6.1 WBI risk assessment -- 2.7 Security design objectives -- 2.7.1 Functional design objectives -- 2.7.2 Non-functional design objectives -- 2.8 Architectural decisions -- Chapter 3. Applying the reference architecture -- 3.1 Solution design and delivery approach -- 3.1.1 Implementation life-cycle -- 3.1.2 Requirements analysis -- 3.1.3 Incremental delivery strategy -- 3.2 WBI solution design.
3.2.1 Solution overview -- 3.2.2 Component model -- 3.2.3 The operational architecture -- 3.2.4 The security architecture -- 3.2.5 Implementation phases -- Chapter 4. Implementing the solution -- 4.1 Development environment overview -- 4.1.1 Component model -- 4.1.2 Operational model -- 4.1.3 Security architecture -- 4.2 Technical implementation -- 4.2.1 Automatic provisioning -- 4.2.2 Application subscription -- 4.2.3 Self care -- 4.2.4 Self registration -- 4.3 Conclusion -- Part 2 Appendixes -- Appendix A. ISO 17799 compliance mapping -- Corporate policy and standards -- Standards, practices, and procedures -- Practical example -- External standards and certifications -- Industry specific requirements -- Product or solution certifications -- Nationally and internationally recognized standards -- Legal requirements -- ISO 17799 and integrated identity management -- Summary -- Glossary -- Related publications -- IBM Redbooks -- How to get IBM Redbooks -- Help from IBM -- Index -- Back cover. |
| Record Nr. | UNINA-9910811279703321 |
|
Bucker Axel
|
||
| Austin, TX, : IBM, International Technical Support Organization, c2004 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||