{"id":91558,"date":"2025-01-06T17:25:12","date_gmt":"2025-01-06T09:25:12","guid":{"rendered":"https:\/\/www.i-sprint.com\/enterprise-access-control\/"},"modified":"2025-03-24T11:25:41","modified_gmt":"2025-03-24T03:25:41","slug":"enterprise-access-control","status":"publish","type":"page","link":"https:\/\/www.i-sprint.com\/ja\/enterprise-access-control\/","title":{"rendered":"\u30a8\u30f3\u30bf\u30fc\u30d7\u30e9\u30a4\u30ba\u30a2\u30af\u30bb\u30b9\u5236\u5fa1"},"content":{"rendered":"

Enterprise Access Control<\/p><\/h1><\/div>

<\/div><\/div><\/div>

Overview<\/p>\n<\/div>

<\/div><\/div><\/div>

The current proliferation of login IDs and passwords is becoming a serious issue in most organizations and is especially critical when customers are accessing multiple e-business systems. This problem can be attributed to a number of factors \u2013 including the heterogeneous computing environments in most large organizations and the lack of comprehensive and intuitive security features in most existing middleware technologies, e.g. DCOM, CORBA, and EJBs. These issues resulted in most software development teams building their own security sub-systems to handle authentication, access rights, and audit trails for their business applications. Most of these home-grown, piecemeal solutions are usually not secure, re-usable or scalable.<\/p>\n

From the security administration perspective, there have been a number of attempts by the industry to implement security administration models. Most of the current solutions suffer from a number of drawbacks and organizations with higher security standards usually resort to manual procedures to enforce segregation of duties and dual control, thus reducing the effectiveness of their security policies for high-risk applications.<\/p>\n

\n
\n

In particular, we have to address the following requirements:<\/p>\n<\/div>\n<\/div>\n

\n