A Defense Industrial Base (DIB) está sob ataque constante de agentes de ameaça sofisticados de Estados-nação. Nem sempre se tratam de eventos de desmantelamento ruidosas e em grande escala; muitas vezes, são ataques "silenciosos e lentos" concebidos para roubar dados sensíveis de forma discreta, que, em conjunto, podem comprometer a segurança nacional. O recente ataque à Stryker, uma importante fabricante de dispositivos médicos com contratos com o governo dos EUA, é um forte lembrete de que todos os elos da cadeia de suprimentos são alvos. Agora, mais do que nunca, fica claro que o DIB precisa reforçar suas defesas em relação às Informações Não Classificadas Controladas (CUI).

Para solucionar isso, o Departamento de Guerra dos EUA (DoW) tem a obrigação de estender seus próprios padrões de segurança rigorosos a toda a cadeia de suprimentos de prestadores de serviços que lidam com informações confidenciais. Proteger essas informações controladas não classificadas (CUI, na sigla em inglês) — seja contra uma violação de dados maliciosa ou simplesmente contra o manuseio interno inadequado — é uma parte direta e imprescindível da defesa da Nação.

A Certificação do Modelo de Maturidade em Segurança Cibernética (CMMC) é a estrutura do Departamento de Defesa para garantir essa proteção. Agora, o CMMC 2.0 é um requisito de conformidade e verificação criado para garantir que todos os prestadores de serviços e subcontratados tenham implementado os padrões de cibersegurança exigidos pelo NIST. Agora, atingir o nível adequado de certificação CMMC será uma condição não negociável para a concessão de um contrato DoW.

A Série: seu Modelo para o Sucesso no CMMC

Embora o CMMC abranja uma ampla gama de domínios de segurança, toda a estrutura é construída sobre uma base de zero trust, e o alicerce da zero trust é a identidade. A Okta é a principal parceira independente em gerenciamento de identidades, e por isso está em uma posição única para ajudar os clientes a conquistar os domínios críticos de controle de acesso (AC) e identificação e autenticação (IA) do CMMC.

Além disso, o Okta pode servir como plataforma central de integração para todo o seu ecossistema de segurança. Por meio de nossas APIs robustas e da Okta Integration Network, permitimos que o senhor conecte sua plataforma de identidade com as outras ferramentas de segurança das quais depende, criando uma defesa coesa e poderosa que também está alinhada aos requisitos do CMMC em vários domínios.

Ao longo desta série de posts no blog, vamos analisar as principais famílias de especificações NIST SP 800-171, que formam a base para o CMMC Nível 2, e NIST SP 800-171, que formam a base para o CMMC Nível 3. Mostraremos não apenas que a Okta pode ajudar, mas como— fornecendo um plano prático que se pode usar para projetar uma arquitetura compatível com o CMMC e detalhando as evidências específicas que podem ser apresentadas a um avaliador para comprovar a conformidade.

  1. Visão geral de Identificação e Autenticação (IA)

Entendendo o que está em jogo: a pontuação do CMMC

É fundamental entender que nem todos os controles CMMC são iguais. O DoW utiliza um sistema de pontuação ponderada no qual os controles valem 1, 3 ou 5 pontos com base em sua importância. Isso significa:

  • A pontuação máxima é 110 pontos.
  • Uma organização pode ser elegível para uma certificação condicional com uma pontuação mínima de 88, desde que todas as lacunas restantes sejam referentes a controles de 1 ponto e estejam documentadas em um Plano de Ação e Marcos (POA&M).
  • Fundamentalmente, o senhor será reprovado na avaliação, independentemente da sua pontuação, se ao menos um dos critérios de controle "Big Rock" de alto valor (que valem 3 ou 5 pontos) estiver "não atendido". Todos esses itens devem estar em total conformidade no momento da auditoria.

Um número significativo desses "grandes desafios" está relacionado à identidade, tornando a escolha de um provedor de identidade uma das decisões mais importantes que o senhor tomará em sua jornada rumo à certificação CMMC. Acompanhe-nos nesta série para aprender como dominá-las.

Consulte a tabela abaixo para obter informações sobre como a Okta ajuda os clientes a atender a esses requisitos.

Observação: esta tabela abrange apenas os controles CMMC 2.0 que o Okta pode atender ou suportar.

 

FamilyLevel 1 IdentifierLevel 2 IdentifierLevel 3 IdentifierScoreOkta ScopeSupporting Product
Access Control (AC)AC.L1-3.1.1
Authorized Access Control

Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).
  5MeetUniversal Directory, Okta Identity Governance
AC.L1-3.1.2
Transaction and Function Control

Limit information system access to the types of transactions and functions that authorized users are permitted to execute.
  5MeetUniversal Directory, Okta Identity Governance, Identity Threat Protection
  AC.L3-3.1.2E
Organizationally Controlled Assets

Restrict access to systems and system components to only those information resources that are owned, provisioned, or issued by the organization.
 MeetUniversal Directory, Okta Device Access, Adaptive Multifactor Authentication
 AC.L2-3.1.3
Control CUI Flow

Control the flow of CUI in accordance with approved authorizations.
 1SupportUniversal Directory, Okta Identity Governance
  AC.L3-3.1.3E
Secured Information Transfer

Employ secure information transfer solutions to control information flows between security domains on connected systems.
  Universal Directory, Okta Identity Governance, API Access Management
 AC.L2-3.1.4
Separation of Duties

Separate the duties of individuals to reduce the risk of malevolent activity without collusion.
 1SupportUniversal Directory
 AC.L2-3.1.5
Least Privilege

Employ the principle of least privilege, including for specific security functions and privileged accounts.
 3MeetUniversal Directory, Okta Identity Governance, Identity Threat Protection
 AC.L2-3.1.6
Non-Privileged Account Use

Use non-privileged accounts or roles when accessing nonsecurity functions.
 1MeetUniversal Directory
 AC.L2-3.1.7
Privileged Functions

Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.
 1MeetUniversal Directory
 AC.L2-3.1.8
Unsuccessful Logon Attempts

Limit unsuccessful logon attempts.
 1MeetUniversal Directory
 AC.L2-3.1.9
Privacy & Security Notices

Provide privacy and security notices consistent with applicable CUI rules.
 1SupportUniversal Directory
 AC.L2-3.1.10
Session Lock

Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity
 1SupportOkta Device Access
 AC.L2-3.1.11
Session Termination

Terminate (automatically) a user session after a defined condition.
 1MeetUniversal Directory, Identity Threat Protection, Okta Device Access
 AC.L2-3.1.13
Remote Access Confidentiality

Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.
 5SupportUniversal Directory
 AC.L2-3.1.15
Privileged Remote Access

Authorize remote execution of privileged commands and remote access to security-relevant information.
 1SupportOkta Identity Governance
 AC.L2-3.1.18
Mobile Device Connection

Control connection of mobile devices.
 5MeetUniversal Directory
Audit and Accountability (AU) AU.L2-3.3.1
System Auditing

Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity.
 5MeetUniversal Directory, Identity Threat Protection
 AU.L2-3.3.2
User Accountability

Ensure that the actions of individual system users, can be uniquely traced to those users so they can be held accountable for their actions.
 3MeetUniversal Directory, Identity Threat Protection
 AU.L2-3.3.3
Event Review

Review and update logged events.
 1SupportUniversal Directory, Identity Threat Protection
 AU.L2-3.3.5
Audit Correlation

Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.
 5SupportUniversal Directory, Identity Threat Protection
 AU.L2-3.3.6
Reduction & Reporting

Provide audit record reduction and report generation to support on-demand analysis and reporting.
 1SupportUniversal Directory, Identity Threat Protection
 AU.L2-3.3.7
Authoritative Time Source

Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.
 1MeetUniversal Directory
 AU.L2-3.3.8
Audit Protection

Protect audit information and audit logging tools from unauthorized access, modification, and deletion.
 1MeetUniversal Directory, Identity Threat Protection
 AU.L2-3.3.9
Audit Management

Limit management of audit logging functionality to a subset of privileged users.
 1MeetUniversal Directory, Identity Threat Protection
Configuration Management (CM) CM.L2-3.4.1
System Baselining

Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.
 5SupportUniversal Directory, Adaptive Multifactor Authentication, API Access Management, Okta Identity Governance, Workflows, Identity Threat Protection, Okta Device Access
 CM.L2-3.4.2
Security Configuration Enforcement

Establish and enforce security configuration settings for information technology products employed in organizational systems.
 5SupportUniversal Directory, Adaptive Multi-factor Authentication, API Access Management, Okta Identity Governance, Workflows, Identity Threat Protection, Okta Device Access
  CM.L3-3.4.2E
Automated Detection & Remediation
N/ASupportAdaptive Multifactor Authentication
 CM.L2-3.4.5
Access Restrictions for Change

Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.
 5SupportUniversal Directory, Okta Identity Governance
Identification and Authentication (IA)IA.L1-3.5.1
Identification

Identify information system users, processes acting on behalf of users, or devices.
  5MeetUniversal Directory
  IA.L3-3.5.1E
Bidirectional Authentication

Identify and authenticate systems and system components, where possible, before establishing a network connection using bidirectional authentication that is cryptographically based and replay resistant.
N/ASupportOkta Device Access
IA.L1-3.5.2
Authentication

Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.
  5MeetUniversal Directory
 IA.L2-3.5.3
Multifactor Authentication

Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.
 1MeetUniversal Directory
  IA.L3-3.5.3E
Block Untrusted Assets

Employ automated or manual/procedural mechanisms to prohibit system components from connecting to organizational systems unless the components are known, authenticated, in a properly configured state, or in a trust profile.
N/ASupportUniversal Directory, Okta Device Access, Adaptive Multifactor Authentication
 IA.L2-3.5.4
Replay-Resistant Authentication

Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.
 1MeetUniversal Directory
 IA.L2-3.5.5
Identifier Reuse

Prevent the reuse of identifiers for a defined period.
 1MeetUniversal Directory
 IA.L2-3.5.6
Identifier Handling

Disable identifiers after a defined period of inactivity.
 1MeetUniversal Directory, Okta Identity Governance, Workflows
 IA.L2-3.5.7
Password Complexity

Enforce a minimum password complexity and change of characters when new passwords are created.
 1MeetUniversal Directory
 IA.L2-3.5.8
Password Reuse

Prohibit password reuse for a specified number of generations.
 1MeetUniversal Directory
 IA.L2-3.5.9
Temporary Passwords

Allow temporary password use for system logons with an immediate change to a permanent password.
 1MeetUniversal Directory
 IA.L2-3.5.10
Cryptographically-Protected Passwords

Store and transmit only cryptographically protected passwords.
 5MeetUniversal Directory, Adaptive Multi-factor Authentication
 IA.L2-3.5.11
Obscure Feedback

Obscure the feedback of authentication information.
 1MeetUniversal Directory
Incident Response  IR.L3-3.6.1E
Security Operations Center
N/ASupportUniversal Directory, Workflows
  IR.L3-3.6.2E
Cyber Incident Response Team
N/ASupportUniversal Directory, Identity Threat Protection, Workflows
Maintenance (MA) MA.L2-3.7.5
Nonlocal Maintenance

Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.
 5MeetUniversal Directory, Adaptive Multi-factor Authentication, Okta Identity Governance
Media Protection (MP) MP.L2-3.8.9
Protect Backups

Protect the confidentiality of backup CUI at storage locations.
 1SupportUniversal Directory, Adaptive Multifactor Authentication, Okta Device Access, API Access Management, Okta Identity Governance, Workflows, Identity Threat Protection
Personnel Security (PS) PS.L2-3.9.2
Personnel Actions

Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers.
 5MeetLifecycle Management
  PS.L3-3.9.2E
Adverse Information

Ensure that organizational systems are protected if adverse information develops or is obtained about individuals with access to CUI.
N/ASupportUniversal Directory, Okta Device Access, Identity Threat Protection, Workflows
Risk Assessment (RA) RA.L2-3.11.2
Vulnerability Scan

Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.
 5SupportUniversal Directory, Adaptive Multifactor Authentication, Okta Device Access, API Access Management, Okta Identity Governance, Workflows, Identity Threat Protection
  RA.L3-3.11.2E
Threat Hunting

Conduct cyber threat hunting activities on an on-going aperiodic basis or when indications warrant, to search for indicators of compromise in organizational systems and detect, track, and disrupt threats that evade existing controls.
N/ASupportUniversal Directory, Identity Threat Protection, Workflows
  RA.L3-3.11.3E
Advanced Risk Identification

Employ advanced automation and analytics capabilities in support of analysts to predict and identify risks to organizations, systems, and system components.
N/ASupportUniversal Directory, Identity Threat Protection, Workflows
  RA.L3-3.11.5E
Security Solution Effectiveness

Assess the effectiveness of security solutions at least annually or upon receipt of relevant cyber threat information, or in response to a relevant cyber incident, to address anticipated risk to organizational systems and the organization based on current and accumulated threat intelligence.
N/ASupportUniversal Directory, Identity Threat Protection, Workflows, Okta Identity Governance
  RA.L3-3.11.6E
Supply Chain Risk Response

Assess, respond to, and monitor supply chain risks associated with organizational systems and system components.
N/ASupportUniversal Directory, Identity Threat Protection, Workflows, Okta Identity Governance
  RA.L3-3.11.7E
Supply Chain Risk Plan

Develop a plan for managing supply chain risks associated with organizational systems and system components; update the plan at least annually, and upon receipt of relevant cyber threat information, or in response to a relevant cyber incident.
N/ASupportUniversal Directory, Identity Threat Protection, Workflows, Okta Identity Governance
Security Assessment (CA) CA.L2-3.12.1
Security Control Assessment

Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.
 5SupportUniversal Directory, Adaptive Multifactor Authentication, Okta Device Access, API Access Management, Okta Identity Governance, Workflows, Identity Threat Protection
 CA.L2-3.12.2
Plan of Action

Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems.
 3SupportUniversal Directory, Adaptive Multifactor Authentication, Okta Device Access, API Access Management, Okta Identity Governance, Workflows, Identity Threat Protection
 CA.L2-3.12.3
Security Control Monitoring

Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.
 5SupportUniversal Directory, Adaptive Multifactor Authentication, Okta Device Access, API Access Management, Okta Identity Governance, Workflows, Identity Threat Protection
System and Communications Protection (SC)SC.L1-3.13.1
Boundary Protection

Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems.
  5SupportUniversal Directory, Adaptive Multifactor Authentication, Okta Device Access, API Access Management, Okta Identity Governance, Workflows, Identity Threat Protection
 SC.L2-3.13.2
Security Engineering

Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.
 5SupportUniversal Directory, Adaptive Multifactor Authentication, Okta Device Access, API Access Management, Okta Identity Governance, Workflows, Identity Threat Protection
 SC.L2-3.13.3
Role Separation

Separate user functionality from system management functionality.
 1MeetUniversal Directory
 SC.L2-3.13.4
Shared Resource Control

Prevent unauthorized and unintended information transfer via shared system resources.
 1SupportUniversal Directory, Adaptive Multifactor Authentication, Okta Device Access, API Access Management, Okta Identity Governance, Workflows, Identity Threat Protection
  SC.L3-3.13.4E
Isolation

Employ physical isolation techniques or logical isolation techniques or both in organizational systems and system components.
N/ASupportUniversal Directory, Okta Identity Governance, Org2Org
 SC.L2-3.13.8
Data in Transit

Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.
 3SupportUniversal Directory, Adaptive Multifactor Authentication, Okta Device Access, API Access Management, Okta Identity Governance, Workflows, Identity Threat Protection
 SC.L2-3.13.11
CUI Encryption

Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.
 1MeetUniversal Directory, Adaptive Multifactor Authentication, Okta Device Access, API Access Management, Okta Identity Governance, Workflows, Identity Threat Protection
System and Information Integrity (SI)  SI.L3-3.14.1E
Integrity Verification

Verify the integrity of security critical and essential software using root of trust mechanisms or cryptographic signatures.
N/ASupportUniversal Directory
 SI.L2-3.14.3
Security Alerts & Advisories

Monitor system security alerts and advisories and take action in response.
 5SupportUniversal Directory, Adaptive Multifactor Authentication, Okta Device Access, API Access Management, Okta Identity Governance, Workflows, Identity Threat Protection
  SI.L3-3.14.6E
Threat-Guided Intrusion Detection

Use threat indicator information and effective mitigations obtained from, at a minimum, open or commercial sources, and any DoD-provided sources, to guide and inform intrusion detection and threat hunting.
N/ASupportUniversal Directory, Identity Threat Protection

Para saber mais sobre como a Okta pode ajudar sua organização a atender aos requisitos do CMMC, baixe nosso Guia de Descoberta do CMMC em https://www.okta.com/resources/datasheet-okta-cmmc-discovery-guide/ ou entre em contato conosco em okta.com/contact-sales/.

Embora este artigo discuta certos conceitos jurídicos, ele não constitui aconselhamento jurídico e não deve ser interpretado como tal. É fornecido apenas para fins informativos. Para obter aconselhamento jurídico sobre as necessidades de conformidade da organização, recomenda-se consultar o departamento jurídico da mesma. A Okta não faz declarações ou oferece qualquer tipo de garantia em relação ao conteúdo deste artigo. Informações sobre as garantias contratuais da Okta para seus clientes podem ser encontradas em okta.com/agreements.

Continue sua jornada de identidade