8.1.3 Denial of service

In a denial of service attack, the attacker's goal is to prevent the directory from providing service to its clients. For example, an attacker might use all the system's resources, thereby preventing these resources from being used by anyone else.

Directory Server can prevent denial of service attacks by setting limits on the resources allocated to a particular bind DN. For more information about setting resource limits based on the user's bind DN, see the "User Account Management" chapter in the HP-UX Directory Server administrator guide.

8.2 Analyzing security needs

Analyze the environment and users to identify specific security needs. The site survey in Chapter 3 “Designing the directory schema” clarifies some basic decisions about who can read and write the individual pieces of data in the directory. This information forms the basis of the security design.

The way security is implemented also depends on how the directory service is used to support the business. A directory that serves an intranet does not require the same security measures as a directory that supports an extranet or e-commerce applications that are open to the Internet.

If the directory only serves an intranet, consider what level of access is needed for information:

How to provide users and applications with access to the information they need to perform their jobs.

How to protect sensitive data regarding employees or the business from general access.

If the directory serves an extranet or supports e-commerce applications over the Internet, there are additional points to consider:

How to offer customers a guarantee of privacy.

How to guarantee information integrity.

The following sections provide information about analyzing security needs.

8.2.1 Determining access rights

The data analysis identifies what information users, groups, partners, customers, and applications need to access the directory service.

Access rights can be granted in one of two ways:

Grant all categories of users as many rights as possible while still protecting sensitive data.

An open method requires accurately determining what data are sensitive or critical to the business.

Grant each category of users the minimum access they require to do their jobs.

A restrictive method requires minutely understanding the information needs of each category of user inside, and possibly outside, of the organization.

Irrespective of the method used to determine access rights, create a simple table that lists the categories of users in the organization and the access rights granted to each. Consider creating a table that lists the sensitive data held in the directory and, for each piece of data, the steps taken to protect it.

For information about checking the identity of users, see “Selecting appropriate authentication methods”. For information about restricting access to directory information, see “Designing access control”

104 Designing a secure directory

Page 104
Image 104
HP UX Direry Server manual Analyzing security needs, Denial of service, Determining access rights

UX Direry Server specifications

HP UX Directory Server is a robust and scalable solution designed for managing directory information within enterprise networks. Developed by Hewlett-Packard (HP), this server offers an extensive set of features tailored to meet the needs of organizations that require an efficient way to store, manage, and retrieve identity and access data.

One of the key features of HP UX Directory Server is its ability to handle large directories with significant volumes of data. Built on a highly optimized architecture, it provides excellent performance and can support millions of entries without sacrificing speed or reliability. This capability makes it an ideal choice for large-scale deployments in enterprises that require high availability and responsiveness.

In addition to its scalability, HP UX Directory Server supports a wide range of protocols, including LDAP (Lightweight Directory Access Protocol), which ensures seamless integration with diverse applications and systems across various platforms. The server maintains standards compliance, which facilitates interoperability and simplifies administration tasks.

Security is a top priority for HP UX Directory Server, offering an array of features to protect sensitive information. It supports secure data transmission via TLS/SSL protocols, ensuring encrypted communication between clients and servers. Advanced access controls allow administrators to define fine-grained permissions, helping to safeguard directory data against unauthorized access.

Another salient feature of HP UX Directory Server is its replication capabilities. The server can replicate directory data across multiple instances, ensuring data consistency and availability in distributed environments. This feature is essential for businesses operating across different geographical locations or requiring failover solutions for disaster recovery.

HP UX Directory Server also comes equipped with tools for data management, including an intuitive administration console for configuring and monitoring the server. Additionally, it offers customizable schema capabilities, enabling organizations to tailor the directory structure to fit their specific needs.

Integration with existing identity management solutions is streamlined through connectors and APIs, allowing organizations to extend their directory services and enhance user experience.

In summary, HP UX Directory Server is a powerful directory management solution that combines scalability, security, and integration flexibility. Its support for industry standards, advanced replication, and comprehensive administrative tools makes it an essential asset for organizations seeking to manage identity and access efficiently. By leveraging this technology, businesses can improve their operational efficiency and ensure a secure and organized approach to directory management.