Service storing and providing identity-related information.

Using multiple layers of security controls.

Security testing of running applications.

Checking software dependencies for vulnerabilities.

Hiding sensitive information while retaining useful structure.

Removing sensitive information from data.

Transforming data to prevent identifying individuals.

Replacing identifying data with pseudonyms.

Controls designed to prevent unauthorized data leakage.

Data useful for investigating digital activity.

Rule identifying potentially suspicious activity.

Analyzing malware while it executes in isolation.

Rule preventing an operation or access.

Organized collection of identity or resource information.

Removing accounts or resources.

Allowing another entity to act with specified permissions.

HTTP method commonly used to remove a resource.

System translating domain names into network addresses.

Human-readable name identifying an internet resource.

Service that resolves domain names.

Entry describing a domain's DNS information.

Administrative portion of the DNS namespace.

Cached DNS resolution information.

Time for which a DNS record may be cached.

Router used to reach other networks.

Architecture spreading software across multiple machines.

Architecture distributing control among multiple nodes.

Architecture organized around shared data resources.

Pattern dynamically adding behavior to objects.

Supplying dependencies from outside a component.

Design principle separating high-level logic from concrete dependencies.

Design approach centered on business domain concepts.

Representation of business concepts and rules.

Service containing domain logic not belonging to an entity.

Event representing something significant in a business domain.

Converting ciphertext back into readable data.

Cryptographic proof of authenticity and integrity.