Enterprise Technology Terminology

5,405 results · page 46 of 271

• Common Criteria for Information Technology Security Evaluation

  Common Criteria for Information Technology Security Evaluation is an ISO/IEC standard framework used to define, implement, and independently evaluate the security properties of IT products, providing structured assurance that supports procurement, compliance, and risk management in enterprise and government environments.

• Common Information Model

  Common Information Model is a standardized, object-oriented data model for representing and exchanging management information about systems, networks, and infrastructure resources, enabling consistent semantics and interoperability across heterogeneous management tools, platforms, and vendors in enterprise IT and service management environments.

• Common Operating Picture

  Common operating picture is a shared, real-time view of operational information that gives authorized stakeholders a consistent understanding of current conditions, resources, and activities across an environment, supporting coordinated decisions in security operations, incident management, and mission-critical enterprise contexts.

• Common Vulnerabilities and Exposures

  Common Vulnerabilities and Exposures is a standardized, publicly available list of disclosed cybersecurity vulnerabilities and exposures, using unique identifiers that let enterprises coordinate vulnerability management, security tooling, compliance activities, and risk reporting across diverse systems, vendors, and regulatory or audit requirements.

• Common Vulnerability Scoring System

  Common Vulnerability Scoring System is a standardized framework for assigning numeric severity scores to software and hardware security vulnerabilities, enabling enterprises to compare issues consistently, prioritize remediation, automate vulnerability management workflows, and align technical findings with organizational risk and compliance practices.

• Communication Service Provider

  Communication service provider is an umbrella term for organizations that deliver regulated voice, data, and media transport services over fixed, mobile, or converged networks, which enterprises depend on for connectivity, network performance, resilience, and compliance across distributed IT, cloud, and communications environments.

• Community Contribution Policy

  Community contribution policy is a formal governance and legal framework that sets rules, workflows, and licensing terms for accepting and managing external contributions to software projects, platforms, or documentation, enabling controlled collaboration while maintaining security, quality, compliance, and clear intellectual property ownership.

• Community Governance Model

  Community governance model is a formalized approach to how a defined community sets and enforces rules, roles, and decision-making processes for shared digital, data, or technology environments, enabling structured collective control, accountability, and policy alignment across multiple stakeholders in enterprise contexts.

• Compliance

  Compliance is the condition and process of conforming to applicable laws, regulations, standards, and internal policies governing how an enterprise operates and manages data, used to control regulatory risk, support audits, and structure technology and security controls.

• Compliance-as-Code

  Compliance-as-Code is the practice of encoding regulatory, security, and internal policy controls as machine-readable code so enterprises can automate compliance checks, evidence collection, and enforcement across infrastructure and applications, supporting continuous governance within DevSecOps and cloud-native operating models.

• Compliance Assessment

  Compliance assessment is a structured process that evaluates how well an organization’s controls, policies, and operations conform to defined legal, regulatory, and standards-based requirements, providing evidence to support risk management, audits, certifications, and continuous improvement of governance and security practices.

• Compliance Audit

  Compliance audit is a formal, independent assessment that tests whether an organization follows defined regulations, standards, contractual clauses, or internal policies. It matters in enterprise environments because it provides documented assurance for boards, regulators, customers, and risk functions about control design and operating effectiveness.

• Compliance Audit Trail

  Compliance audit trail is a tamper-evident, time-ordered record of system and user activities that documents how controls operate, enabling organizations to demonstrate regulatory and policy compliance, support audits and investigations, and maintain accountability for access and changes in enterprise systems.

• Compliance by Design

  Compliance by Design embeds regulatory, legal, and policy requirements into system and process design from the outset, enabling organizations to implement, enforce, and evidence compliance through built-in controls, automation, and monitoring across architectures, platforms, and workflows.

• Compliance Data Zone

  Compliance data zone is a bounded data environment that enforces regulatory, legal, and policy controls for storing and processing regulated or high-sensitivity data in enterprises, enabling structured governance, auditability, and risk management across analytics, applications, and hybrid or cloud architectures.

• Compliance Framework

  Compliance framework is a structured set of guidelines, controls, and processes that organizations use to organize and implement requirements from laws, regulations, and standards, enabling consistent governance, security, and privacy practices and supporting audits, certifications, and compliance reporting in enterprise environments.

• Compliance Monitoring

  Compliance monitoring is the ongoing assessment of whether an organization’s controls and activities conform to applicable laws, regulations, standards, and internal policies, providing evidence to management, auditors, and regulators and supporting remediation when control gaps or nonconformities are identified.

• compliance pipeline

  Compliance pipeline is an automated sequence of regulatory, security, and governance checks embedded into software delivery or data workflows, used by enterprises to enforce documented policies, prevent noncompliant changes, and generate audit-ready evidence during continuous integration, deployment, and operations.

• Component Refurbishment

  Component refurbishment is the controlled process of restoring used hardware or mechanical components to a documented, reusable condition that meets defined specifications, supporting lifecycle management, cost control, and continuity of operations in enterprise, industrial, and regulated technical environments.

• Components

  Components are modular, encapsulated units in software, hardware, or system architectures that expose defined interfaces and deliver specific functionality, enabling enterprises to decompose complex systems into manageable building blocks for reuse, governance, security assessment, and independent deployment and change control.