Blog Category: Identity Management
from centralizing password storage, to enabling a greater degree of regulatory compliance, OPAM provides several key features that are crucial to properly mitigating security risks and preventing security holes regarding the management and use of privileged accounts. This Oracle product should be seriously considered as a complement to any existing Identity Governance implementations or even as a stand alone product for those organizations who aren't currently invested in Oracle Identity.
In this age of internet security issues, it is an increasingly common task for Zirous’ clients to implement improved system security for their web-based applications and services. Often, a key component of this is to create a user self-service capability.
Identity Management (IdM) is a term that defines a collection of processes and activities surrounding the management of records about identities for the purpose of controlling access (authentication) and privileges (authorization) within or across multiple computer systems. Self-Service is a subset of features within Identity Management that defines activities a user can do with a computer system on their own, without reaching out to helpdesk or IT personnel. Here are seven common Self-Service features, their typical use cases, and some some concepts that are important when implementing Self-Service features in an IdM solution.
Database Administrators, are you constantly managing your users and making changes in 50 or more databases? Zirous understands that your time is valuable, so stop wasting it! There is no time for manually changing and creating these user privileges. Oracle Enterprise User Security (EUS) allows your company to manage database users and their authorizations in one central location.
Zirous was chosen as a Top Oracle Solutions Provider in CIOReview magazine's September 15th issue
Recently, I supported two projects that required the use of Oracle Identity Manager Flat File connector. Each project had very different requirements. One project required a disconnected resource and the other, reconciliation of PeopleSoft data. In this blog post I will describe the two problems and how I used the Flat File connector to overcome them.
The Company had an existing tool as part of their website where customers were able to create an online account in order to customize certain products for their home. The Company wished to have a unified view of their customers across all phases of this sales cycle.
The Business needed to make their request processes automated. Instead of filling out forms and sending handfuls of emails, the process needed to be centralized so everything is requested through one tool and that one tool grants access. In a business where time equals money, this process can bring major cost savings, especially when it comes to password maintenance and reduced help desk calls.