Identity Automation Blog

Stay up to date with all of the latest news and events.

In today’s digital world, information security has quickly become one of the foremost areas of concern for individuals and businesses alike. Particularly in the business realm, government regulations, such as the Payment Card Industry Data Security Standard (PCI DSS) and the Health Insurance Portability and Accountability Act (HIPAA), require close security auditing and penetration testing in order to ensure consumer, patient, and business data are handled securely (i.e. storage, retrieval, transmission, and authorized access).

Launching new IT initiatives is always a challenge, and the roll-out and adoption of a new identity and access management (IAM) program is no exception. While you understand how your IAM solution will better secure your organization and data and make getting work done easier, your co-workers don’t always look positively on change.

At the highest level, identity management systems are typically composed of three major elements: users, systems/applications, and policies. Policies define how the users interact with the different systems and applications.

As a marketing professional one of the most important jobs my team and I perform is building support and loyalty around our company’s brand. Building a brand the right way helps to create a strong community that believes strongly in our products, ultimately creating evangelists. Effective branding contributes to getting people fired up and ready to buy.

In previous installments of this series, we discussed the emergence of Identity as a Service (IDaaS) and the benefits it offers. We also cleared up some of the most common misconceptions surrounding IDaaS. Now that you have a better understanding of the technology and its potential, let’s examine the most common IDaaS models, so that you can choose the right one for your organization.

In our last post, we discussed some of the most compelling reasons for adopting identity and access management (IAM) in the cloud. Like most other cloud services, identity as a service (IDaaS) offers cost-effective, high availability and affordable scalability. However, as you consider the possibility of moving from your legacy, on-premises IAM system to the cloud, it’s vital that you begin with a clear understanding of common misperceptions that haunt the emerging IDaaS market; here are the two biggest ones:

Today, I want to look at one of the ways that RapidIdentity allows administrators to automate tedious and cumbersome tasks. I’ll demonstrate a way to analyze Windows domain controllers for the presence of a specific software installation and also provide the entire RapidConnect action at the end of the post, so that you can modify it to fit your needs.

When organizations start or plan to start a new IAM initiative, one of the first steps they take is some form of requirements gathering. The idea is that the requirements represent the functional and nonfunctional (IAM) needs of an organization. Then, typically through some form of procurement, the organization attempts find a solution/service/product(s) that best aligns with those requirements.

Recently, one of our RapidIdentity customers ran into a conundrum. While the customer heavily uses RapidConnect to synchronize their various application and authentication identity sources, they awoke to a mass Email stating that during their morning provisioning the displayName attribute on every user in their environment was changing!

Information technology teams tend to have a lot on their plate in terms of installing, maintaining, and protecting various systems throughout the enterprise. The larger the environment, the darker the cloud that tends to loom overhead when it comes to managing even trivial tasks, such as installing management agents or antivirus and keeping them up-to-date. Typically, this is due to the fact that there simply aren’t enough hands on the team, nor hours in the day, to touch dozens or hundreds of machines in disparate datacenters.