Saturday, March 17, 2012

Digital Rights Management

What is DRM?

Digital Rights Management (DRM) Combination of 3 controls
·         Identity Control
·         Cryptographic Control
·         Access Control
Why we need a DRM solution
Now World Wide Web has become the most popular mode of media content distribution like the following:
·         Audio: Music & Audio books
·         Video: Movies & Music Videos
·         Publishing: books, documents, news articles
·         Computer Games
·         Software
The challenges of Media & Entertainment Industry
The main challenges the Media & Entertainment Industry facing are as follows:
·         Preventing Piracy in Music & Video contents
·         The quality of the Video content on the web
·         Security of the Video/audio content shared on the web
·         Convenient access to the entertainment content on the web
·         Supporting number of platforms to reach target audience

DRM Process
The DRM process I s essentially consists of creating following components:
·         A Content Protection Software
·         A Content Distribution Server
·         A License server
·         A Content Viewer

DRM Process Flow
The DRM Process Flow is depicted in the following diagram:

DRM Tools & Technology
The followings are the main players in the DRM Tools & Technology space:

·         Apple’s Fairplay DRM for online music
·         Adobe Flash & Microsoft Silverlight for Online Videos
·         Widevine provides Digital media solutions for device deliveries
·         Microsoft’s PlayReady platform for Mobile operators
·         Buy DRM


Identity Management with Active Directory - Part 2

Identity Management with Active Directory

AD User


When using AD as Identity store, each identity in the organization will have a AD User account created in AD. Properties such as organizational hierarchy, membership details, telephone and other contact details etc can be assigned to an AD user account.

AD Group


Groups are Active Directory (or local computer) objects that can contain users, contacts, computers, and other groups. Groups can be nested, that is, a group can be a member of another group.

There are two types of groups, Distribution groups and Security groups. Distribution groups are used to create e-mail distribution lists. Distribution groups are used with e-mail applications (such as Microsoft Exchange) to send e-mail to the members of the group. Security groups are an essential component of the relationship between users and security. Security groups are used to manage user and computer access to shared resources and to filter Group Policy settings.

Security Groups are used to create roles and this will be used at the time of access provisioning.

Authorization Manager (AzMan)

Authorization Manager (commonly known as AzMan) is a general-purpose role-based security architecture for Windows. Azman can be used in any application that needs role-based authorization, including ASP.NET Web apps or Web Services, client-server systems based on .NET Remoting etc.
The benefit of using AzMan is that it enables you to define operations, group them into tasks, and then authorize roles to perform specific tasks. It also provides an administrative console for managing roles, tasks, operations, and users.
AzMan supports platform features such as Active Directory (AD) groups, Windows security auditing, and MMC. AzMan assures the proper integration of system access control objects such as the NT access token and better alignment for future Windows access control features such as provisioning and entitlement engines.

Identity Management Life Cycle


When a new employee is recruited in an organization, an identity is created in Active Directory in the form of AD user account. All the roles will have corresponding AD Security Groups created.
When a new role is created in the enterprise application, a corresponding AD Group will be created in AD. And in AzMan policy store, tasks for that particular role will be created.

The provisioning will be done thru a provisioning application which takes the user’s request for access and route the request thru a pre-defined workflow (which is developed and maintained by BizTalk server or any custom .net application built using Windows Workflow (WF in .net framework 3.5). After the approval the user’s AD user account will be added in the corresponding AD Group by the provisioning application using LDAP.

When the user ask for an access in the enterprise application, the Access Management module which used to check the access for the user for the requested functionality will use the AzMan to verify his access rights to the requested functionality.

The Access Management module can be de-coupled from the application logic and can be a stand-alone application. This will give a benefit of a centrally managed Access Control mechanism. And this will help if there is a need of any other way managing access/identity other than AD/AzMan for some set of non-Microsoft applications.

Identity Management with Active Directory - Part 1

Introduction
This post discusses managing identities with Active Directory and Access Management with Microsoft Authorization Manager.
This gives a small introduction of Active Directory components used for Identity Management and this also explains ideal scenarios in Identity Management and Access Management.
What’s Identity Management?
Identity management is a set of systems which manages the users, their accesses, roles etc for enterprises, with significant implications to security and risk strategy. And it is not just a technology discussion as much as it is a process about the role of “roles” in enterprises — how people and applications access.

Identity management is comprised of both technology components and business strategies and policies
The benefits of identity management solution can be gained by consolidating identity, policy and infrastructure management into a single centralized solution, thereby saving time and money in administrative overhead, lowering training requirements and increasing productivity.

Why Active Directory

Since Active Directory is an integral part of Windows infrastructure and networking, it has already become an important and irreplaceable component within the IT environment. And many organizations have already made investments to migrate to Active Directory and deploy it companywide. It makes good business sense to fully leverage those investments by extending Active Directory to other platforms, versus the cost of trying to maintain different solutions for different platforms.

UNIX, Linux and Mac platforms are the second largest base of systems in many large companies, so the ability of Active Directory in integrating with these systems made it a best choice in Enterprise Identity Management.

The solid support from Microsoft – the largest software company in the world is also one of the main reasons to use Active Directory. Microsoft is firmly committed to Active Directory and continues to invest in enhancing and expanding its capabilities.

Considering these strong reasons, Active Directory would be an excellent choice to provide centralized, cross-enterprise directory and infrastructure services for Identity Management in enterprises. The only demerit is that, it does not include capabilities to easily support non-Windows client systems. However, the solution landscape has recently changed, and there is now a way to extend the features and benefits of Active Directory to non-Windows systems and applications. Centrify’s DirectControl suite includes all of the necessary software to allow UNIX, Linux, Mac and Java environments to use Active Directory as a central user identity, infrastructure and policy engine.
And Active Directory’s highly secure, token-based authentication, using industry standard Kerberos, can be used across Windows, UNIX, Linux, Mac and Java platforms. This results in a single sign-on experience that spans all Windows, UNIX and Linux systems.

Active Directory is based on proven enterprise-ready technologies – LDAP for directory services and Kerberos for secure authentication. Microsoft has uniquely combined the strengths of these two technologies to best leverage the open extensibility of LDAP and the highly secure, ticket-based authentication of Kerberos.
For example, a key advantage of Active Directory’s ticket-based authentication system is that, once the user has successfully logged into a system, his or her credentials can be used to automatically access other systems and applications based on established security access rights.

Microsoft’s Group Policy capability extends Active Directory beyond identity and access management to policy and configuration management, which is crucial for meeting regulatory requirements. Administrators have full multi-level control over applying policies to accounts and systems through the Group Policy system.

Active Directory is highly scalable and secure. Active Directory’s distributed model automatically replicates information to other sites, even over slow links, thereby ensuring both fault tolerance with automated failover and increased performance through automated discovery of the closest Active Directory server.
Active Directory has following advantages:
The followings are some of the key advantages of Active Directory.

 ·         Centralized user and group account management

It can store the organizational relationships such as manager - worker relationships.

 ·         Full control over password management
This include password aging, password complexity, and forced password resetting, as well as the ability to temporarily disable an account. Active Directory can also easily manage hours of use for each user and computer.
·         A distributed model for high availability, increased performance and organizational compartmentalization

It has the ability to manage cross domain relationships and trusts. This means that users in each part of the organization can always access their systems, even in the event of a server failure.