Paramify

Controls

We take security, compliance, and privacy seriously. Explore our certifications, reports, and policies in one place.
⌘K

IL5

Paramify Cloud is a cloud-based platform that streamlines compliance reporting and documentation for cloud service providers. It centralizes control, automates workflows, and ensures alignment with FedRAMP requirements, enhancing efficiency, accuracy, and security in compliance processes.

AC-12(1)

Pending
Provide a logout capability for user-initiated communications sessions whenever authentication is used to gain access to .

AC-12(2)

Pending
Display an explicit logout message to users indicating the termination of authenticated communications sessions.

AC-16(6)

Pending
Require personnel to associate and maintain the association of with in accordance with .

AC-16(7)

Pending
Provide a consistent interpretation of security and privacy attributes transmitted between distributed system components.

AC-16 Part a

Pending
Provide the means to associate with for information in storage, in process, and/or in transmission.

AC-16 Part b

Pending
Ensure that the attribute associations are made and retained with the information.

AC-16 Part c

Pending
Establish the following permitted security and privacy attributes from the attributes defined in [AC-16a](#ac-16_smt.a) for : .

AC-16 Part d

Pending
Determine the following permitted attribute values or ranges for each of the established attributes: .

AC-16 Part e

Pending
Audit changes to attributes.

AC-16 Part f

Pending
Review for applicability .

AC-17(10)

Pending
Implement to authenticate .

AC-17(9)

Pending
Provide the capability to disconnect or disable remote access to the system within .

AC-20(3)

Pending
Restrict the use of non-organizationally owned systems or system components to process, store, or transmit organizational information using .

AC-3(4) Part a

Pending
Enforce over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information can do one or more of the following pass the information to any other subjects or objects.

AC-3(4) Part b

Pending
Enforce over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information can do one or more of the following grant its privileges to other subjects.

AC-3(4) Part c

Pending
Enforce over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information can do one or more of the following change security attributes on subjects, objects, the system, or the system’s components.

AC-3(4) Part d

Pending
Enforce over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information can do one or more of the following choose the security attributes to be associated with newly created or revised objects.

AC-3(4) Part e

Pending
Enforce over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information can do one or more of the following change the rules governing access control.

AT-2(4)

Pending
Provide literacy training on recognizing suspicious communications and anomalous behavior in organizational systems using .

AT-2(5)

Pending
Provide literacy training on the advanced persistent threat.

AT-2(6) Part a

Pending
Provide literacy training on the cyber threat environment.

AT-2(6) Part b

Pending
Reflect current cyber threat information in system operations.

AT-3(1)

Pending
Provide with initial and training in the employment and operation of environmental controls.

AT-3(2)

Pending
Provide with initial and training in the employment and operation of physical security controls.

AT-6

Pending
Provide feedback on organizational training results to the following personnel : .

AU-14(1)

Pending
Initiate session audits automatically at system start-up.

AU-14 Part a

Pending
Provide and implement the capability for to the content of a user session under .

AU-14 Part b

Pending
Develop, integrate, and use session auditing activities in consultation with legal counsel and in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.

CA-7(3)

Pending
Employ trend analyses to determine if control implementations, the frequency of continuous monitoring activities, and the types of activities used in the continuous monitoring process need to be modified based on empirical data.

CA-7(5)

Pending
Employ the following actions to validate that policies are established and implemented controls are operating in a consistent manner: .

CA-7(6)

Pending
Ensure the accuracy, currency, and availability of monitoring results for the system using .

CA-8(3)

Pending
Employ a penetration testing process that includes attempts to bypass or circumvent controls associated with physical access points to the facility.

CM-11(2)

Pending
Allow user installation of software only with explicit privileged status.

CM-7(3)

Pending
Ensure compliance with .

GR-10

Pending
How robust is the CSP’s required boundary protection (defense-in-depth security/protective measures) implemented between the internet and the CSO for its protection from internet-based threats?

GR-1 Part a

Pending
Does the CSO enforce DoD PKI (in accordance with DoDI 8520.03) for the authentication of both privileged and non-privileged users? This includes both the use of CAC physical tokens or Alt tokens, as well as DoD certificate revocation resources.

GR-1 Part b

Pending
Is the CSO DoD PK-enabled for their customer ordering/service management portals for all service offerings?

GR-1 Part c

Pending
If the CSO is a SaaS, is the CSO DoD PK-enabled for general DoD user access?

GR-2

Pending
How will the CSO support DoD IP addressing implementation? Plan of action for implementation should be described below.

GR-3

Pending
Does the CSO ensure that all DoD data remains in the States, districts, territories, and outlying areas of the United States and hence ensuring that the data remain under U.S. jurisdiction at all times?

GR-4

Pending
Is the CSO management/monitoring plane (and/or specific devices/systems) integrated with the CSP’s corporate network or the general commercial CSO management plane? If so, how is the management plane connectivity implemented.

GR-5 Part a

Pending
Does the CSP establish position sensitivity risk determinations based on OPM guidance and the Position Sensitivity Tool?

GR-5 Part b

Pending
How does the CSP restrict potential access to DoD information to U.S. Citizens?

GR-5 Part c

Pending
Are all CSO roles with access to DoD CUI categorized as critical sensitive been subject to a satisfactory Single Scope Background Investigation or other background investigation for high risk?

GR-5 Part d

Pending
Are other CSO roles categorized as moderate risk position designations with access to non-critical sensitive information subject to a satisfactory moderate risk background investigation or a National Agency Check with Law and Credit?

GR-6

Pending
How will the CSP/CSO obtain a private connection capability between the off-premises CSP’s/CSO’s network and DoD networks in support of connections through the boundary cloud access point (BCAP) and meet-me points?

GR-7 Part a

Pending
What is the CSO or user experience reliance on internet-based capabilities such as the public DNS or content delivery networks?

GR-7 Part b

Pending
How are such capabailities available via the CSO infrastructure and the connections to it via the DISA BCAPs?

GR-8 Part a

Pending
What is the reliance on internet access to reach the CSO management/service-ordering portal or API endpoints from either NIPRNet or from within the CSO?

GR-8 Part b

Pending
How are all such capabilities available via the CSO infrastructure and the connections to it via the DISN BCAPs?

GR-9

Pending
What are the protections in place in the CSP’s network and CSO to prevent any internet connection to the CSP’s/CSO’s network and CSO from becoming a back door to the NIPRNet via the private connection through the BCAP?

IA-10

Pending
Require individuals accessing the system to employ under specific .

IA-12(1)

Pending
Require that the registration process to receive an account for logical access includes supervisor or sponsor authorization.

IA-3(1)

Pending
Authenticate before establishing connection using bidirectional authentication that is cryptographically based.

IA-4(9)

Pending
Maintain the attributes for each uniquely identified individual, device, or service in .

IA-5(14)

Pending
For PKI-based authentication, employ an organization-wide methodology for managing the content of PKI trust stores installed across all platforms, including networks, operating systems, browsers, and applications.

IA-5(16)

Pending
Require that the issuance of be conducted before with authorization by .

IA-9

Pending
Uniquely identify and authenticate before establishing communications with devices, users, or other services or applications.

IR-4(10)

Pending
Coordinate incident handling activities involving supply chain events with other organizations involved in the supply chain.

IR-4(12)

Pending
Analyze malicious code and/or other residual artifacts remaining in the system after the incident.

IR-4(13)

Pending
Analyze anomalous or suspected adversarial behavior in or related to .

IR-4(14)

Pending
Establish and maintain a security operations center.

IR-4(3)

Pending
Identify and take the following actions in response to those incidents to ensure continuation of organizational mission and business functions: .

IR-4(7)

Pending
Coordinate an incident handling capability for insider threats that includes the following organizational entities .

IR-4(8)

Pending
Coordinate with to correlate and share to achieve a cross-organization perspective on incident awareness and more effective incident responses.

IR-6(2)

Pending
Report system vulnerabilities associated with reported incidents to .

IR-7(2) Part a

Pending
Establish a direct, cooperative relationship between its incident response capability and external providers of system protection capability.

IR-7(2) Part b

Pending
Identify organizational incident response team members to the external providers.

MA-3(5)

Pending
Monitor the use of maintenance tools that execute with increased privilege.

MA-3(6)

Pending
Inspect maintenance tools to ensure the latest software updates and patches are installed.

MA-4(6)

Pending
Implement the following cryptographic mechanisms to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications: .

MA-5(5)

Pending
Ensure that non-escorted personnel performing maintenance activities not directly associated with the system but in the physical proximity of the system, have required access authorizations.

PL-7 Part a

Pending
Develop a Concept of Operations (CONOPS) for the system describing how the organization intends to operate the system from the perspective of information security and privacy.

PL-7 Part b

Pending
Review and update the CONOPS .

PL-8(1) Part a

Pending
Design the security and privacy architectures for the system using a defense-in-depth approach that allocates to .

PL-8(1) Part b

Pending
Design the security and privacy architectures for the system using a defense-in-depth approach that ensures that the allocated controls operate in a coordinated and mutually reinforcing manner.

PL-8(2)

Pending
Require that allocated to are obtained from different suppliers.

PS-3(4)

Pending
Verify that individuals accessing a system processing, storing, or transmitting meet .

RA-10 Part a

Pending
Establish and maintain a cyber threat hunting capability to: 1. search for indicators of compromise in organizational systems; and 2. detect, track, and disrupt threats that evade existing controls.

RA-10 Part b

Pending
Employ the threat hunting capability .

RA-3(2)

Pending
Use all-source intelligence to assist in the analysis of risk.

RA-3(3)

Pending
Determine the current cyber threat environment on an ongoing basis using .

RA-5(10)

Pending
Correlate the output from vulnerability scanning tools to determine the presence of multi-vulnerability and multi-hop attack vectors.

SA-3(1)

Pending
Protect system preproduction environments commensurate with risk throughout the system development life cycle for the system, system component, or system service.

SA-4(7) Part a

Pending
Limit the use of commercially provided information assurance and information assurance-enabled information technology products to those products that have been successfully evaluated against a National Information Assurance partnership (NIAP)-approved Protection Profile for a specific technology type, if such a profile exists.

SA-4(7) Part b

Pending
Require, if no NIAP-approved Protection Profile exists for a specific technology type but a commercially provided information technology product relies on cryptographic functionality to enforce its security policy, that the cryptographic module is FIPS-validated or NSA-approved.

SA-8(1)

Pending
Implement the security design principle of clear abstractions.

SA-8(10)

Pending
Implement the security design principle of hierarchical trust in .

SA-8(11)

Pending
Implement the security design principle of inverse modification threshold in .

SA-8(12)

Pending
Implement the security design principle of hierarchical protection in .

SA-8(13)

Pending
Implement the security design principle of minimized security elements in .

SA-8(14)

Pending
Implement the security design principle of least privilege in .

SA-8(15)

Pending
Implement the security design principle of predicate permission in .

SA-8(16)

Pending
Implement the security design principle of self-reliant trustworthiness in .

SA-8(17)

Pending
Implement the security design principle of secure distributed composition in .

SA-8(18)

Pending
Implement the security design principle of trusted communications channels in .

SA-8(19)

Pending
Implement the security design principle of continuous protection in .

SA-8(2)

Pending
Implement the security design principle of least common mechanism in .

SA-8(20)

Pending
Implement the security design principle of secure metadata management in .

SA-8(21)

Pending
Implement the security design principle of self-analysis in .

SA-8(22)

Pending
Implement the security design principle of accountability and traceability in .

SA-8(23)

Pending
Implement the security design principle of secure defaults in .

SA-8(24)

Pending
Implement the security design principle of secure failure and recovery in .

SA-8(25)

Pending
Implement the security design principle of economic security in .

SA-8(26)

Pending
Implement the security design principle of performance security in .

SA-8(27)

Pending
Implement the security design principle of human factored security in .

SA-8(28)

Pending
Implement the security design principle of acceptable security in .

SA-8(29)

Pending
Implement the security design principle of repeatable and documented procedures in .

SA-8(3)

Pending
Implement the security design principles of modularity and layering in .

SA-8(30)

Pending
Implement the security design principle of procedural rigor in .

SA-8(31)

Pending
Implement the security design principle of secure system modification in .

SA-8(32)

Pending
Implement the security design principle of sufficient documentation in .

SA-8(4)

Pending
Implement the security design principle of partially ordered dependencies in .

SA-8(5)

Pending
Implement the security design principle of efficiently mediated access in .

SA-8(6)

Pending
Implement the security design principle of minimized sharing in .

SA-8(7)

Pending
Implement the security design principle of reduced complexity in .

SA-8(8)

Pending
Implement the security design principle of secure evolvability in .

SA-8(9)

Pending
Implement the security design principle of trusted components in .

SA-9(3)

Pending
Establish, document, and maintain trust relationships with external service providers based on the following requirements, properties, factors, or conditions: .

SA-9(6)

Pending
Maintain exclusive control of cryptographic keys for encrypted material stored or transmitted through an external system.

SA-9(7)

Pending
Provide the capability to check the integrity of information while it resides in the external system.

SA-9(8)

Pending
Restrict the geographic location of information processing and data storage to facilities located within in the legal jurisdictional boundary of the United States.

SC-12(6)

Pending
Maintain physical control of cryptographic keys when stored information is encrypted by external service providers.

SC-16

Pending
Associate with information exchanged between systems and between system components.

SC-18(2)

Pending
Verify that the acquisition, development, and use of mobile code to be deployed in the system meets .

SC-28(3)

Pending
Provide protected storage for cryptographic keys .

SC-38

Pending
Employ the following operations security controls to protect key organizational information throughout the system development life cycle: .

SC-46

Pending
Implement a policy enforcement mechanism between the physical and/or network interfaces for the connecting security domains.

SC-7(13)

Pending
Isolate from other internal system components by implementing physically separate subnetworks with managed interfaces to other components of the system.

SC-7(14)

Pending
Protect against unauthorized physical connections at .

SC-7(15)

Pending
Route networked, privileged accesses through a dedicated, managed interface for purposes of access control and auditing.

SC-8(2)

Pending
Maintain the of information during preparation for transmission and during reception.

SI-12(3)

Pending
Use the following techniques to dispose of, destroy, or erase information following the retention period: .

SI-21

Pending
Refresh at or generate the information on demand and delete the information when no longer needed.

SI-4(15)

Pending
Employ an intrusion detection system to monitor wireless communications traffic as the traffic passes from wireless to wireline networks.

SI-4(24)

Pending
Discover, collect, and distribute to , indicators of compromise provided by .

SI-4(25)

Pending
Provide visibility into network traffic at external and key internal system interfaces to optimize the effectiveness of monitoring devices.

SR-3(1)

Pending
Employ a diverse set of sources for the following system components and services: .

SR-3(2)

Pending
Employ the following controls to limit harm from potential adversaries identifying and targeting the organizational supply chain: .

SR-3(3)

Pending
Ensure that the controls included in the contracts of prime contractors are also included in the contracts of subcontractors.

SR-4

Pending
Document, monitor, and maintain valid provenance of the following systems, system components, and associated data: .

SR-5(1)

Pending
Employ the following controls to ensure an adequate supply of : .

SR-5(2)

Pending
Assess the system, system component, or system service prior to selection, acceptance, modification, or update.

SR-6(1)

Pending
Employ of the following supply chain elements, processes, and actors associated with the system, system component, or system service: .

SR-7

Pending
Employ the following Operations Security (OPSEC) controls to protect supply chain-related information for the system, system component, or system service: .