IEC 62443 Compliance2021-09-02T13:28:09+00:00

IEC 62443 Assessment &

Compliance Software

Rizkly is effective and efficient solution for securing industrial automation and control systems. Whether it’s a small 200 square foot print shop or a global network of critical sites, Rizkly lets you quickly implement a cybersecurity compliance program within weeks to ensure that your industrial automation and controls systems are safer and compliant with IEC 62443 requirements.  Rizkly experts help you with expedited assessment and scoring activities.  You can take if further by assigning specific security and operational controls to one or more vendors and streamline the ongoing tracking and management of their status.  Rizkly also eases the the activities that go with ensuring your suppliers safeguard critical information so you achieve confidence that actions are underway to achieve better security and compliance.

Rizkly’s ability to assist small and large enterprises means you and your suppliers will not be overwhelmed.  Rizkly includes the guidance, templates, task assignment and tracking into one solution to make it the right choice for enabling your supply chain to comply with your requirements.   Rizkly expert advisors will help your vendors come up to speed on best practices, practical remediation methods and tailoring included policy/procedure templates to ensure effective security controls.   Role based access controls means your IEC 62443 compliance initiative can involve many different vendors, advisors and assessors…each with specific permissions and views of information.

What’s Included

  • Supports industrial automation and control system compliance frameworks (IEC 62443, NIST 800-161, ISO, NERC CIP-013-1. CMMC, etc.) or create your own

  • Assessment and surveys to quickly identify boundaries and sensitive information

  • Secure cloud app for managing continuous compliance, evidence capture, policies and procedures

  • Dashboards and alerts to ensure completion and tracking of required NIST 800-171 controls

  • Automatic System Security Plan (SSP) and Plan of Action & Milestones (POA&M) Generation

  • Ongoing Advisory, Coaching, PMO and Quarterly CISO Reviews

  • Scoring and SPRS submission report to ease compliance with the CMMC Interim Rule (DFARS Case 2019-D041)

  • One-click migration with auto control population when if you transition to any level of CMMC

Need More Information?

    Benefits

    • Supply Chain/Vendor Compliance Program Management: Manage and entire supply chain compliance program in one place.  Streamline collaboration between you and your vendors and easily track status and risks.

    • Tasking and Tracking: Assign ownership and access compliance status with a few clicks. Users receive alerts when it’s time to review controls or attach evidence

    • Compliance Audit Documentation: One-click creation of audit-ready documentation such as System Security Plans (SSP), DFARS control scoring and Incident Response Plans  (IRP) reduces the time and effort needed to create, review, and maintain compliance documents, letting you focus on implementing security, rather than documenting it

    • Role-Based Access: streamline the compliance collaboration with your suppliers while providing them with an effective and efficient solution to achieve your compliance requirements.  Learn more about all of the features that make Rizkly the perfect vendor supply chain solution here.


    Rizkly Cybersecurity Compliant badge for our customers

    Rizkly Compliance eBook and Datasheet 

    Questions about supply chain compliance and

    how to quickly roll out a program?  

    We will pick up the phone and give you a call to discuss your needs. 

    What is OSCAL and its role in FedRAMP Automation?2023-08-16T16:05:25+00:00

    By Chor-Ching Fan

    FedRAMP automation is on its way.  The Open Security Controls Assessment Language (OSCAL) is a machine-readable information exchange format developed by the National Institute of Standards and Technology (NIST) to enable automation of risk management and compliance frameworks based on security controls and functional requirements. OSCAL support the expression of compliance information through XML, JSON and YAML formats.  OSCAL was released in June 2021 and is currently in Version 1.1.0 (late July 2023)

    The FedRAMP cybersecurity management program is the first key adopter of the OSCAL standard.  OSCAL promises to enable FedRAMP automation (and other frameworks that adopt it) improving the efficiency and effectiveness of compliance management by providing a standardized, machine-readable format for capturing and sharing security information.  OSCAL automation has the ability to simplify many of the manual tasks involved in compliance including:

    • Generating security documentation
    • Assessment plan and results evaluation
    • Tracking remediation activities
    • Reporting on compliance status

    OSCAL can be used to support a wide range of compliance frameworks, including:

    • FedRAMP (early adoption in progress)
    • NIST Cybersecurity Framework (CSF)
    • ISO/IEC 27001
    • SOC 2
    • HIPAA
    • PCI DSS

    FedRAMP automation with OSCAL promises to be significant improvement over previous approaches to compliance automation.  As proven by similar information exchange automation initiatives in other industries i.e. ecommerce supply chain documents or financial filing with the SEC,  OSCAL should make compliance management be more efficient, more effective, and more scalable.

    Here are some of the benefits of using the new OSCAL compliance framework:

    • Efficiency: OSCAL automation will reduce manual tasks involved in compliance, such as generating security documentation, conducting assessments, and tracking remediation activities. This can save organizations a significant amount of time and money.  FedRAMP SSPs can easily run 300+ pages in Microsoft Word.  With continual updates and document submissions to the FedRAMP PMO,  this task alone will benefit greatly from OSCAL.
    • Effectiveness: OSCAL provides a standardized, machine-readable format for capturing and sharing security information. This makes it easier to identify, evaluate and determine next steps to remediate key risks for the US government and cloud service providers.
    • Scalability & Extensibility: OSCAL is a scalable framework that can be used to support a wide range of compliance frameworks.  OSCAL is extensible so any user or standards body can leverage the reference models while ensuring it supports the unique elements of their own privacy and security risk program.

    Since its 1.0 release in 2021,  Rizkly has supported the OSCAL standard with the goal of providing the best software for FedRAMP automation.  We love OSCAL and think its great for the cybersecurity compliance world.  Companies (CSPs) can import their existing Word SSPs and generate OSCAL with one-click in Rizkly.  It will not be practical for most organizations to use XML editors and handcraft OSCAL files each time there are updates or submission requirements.  While still in a pre-commercialization status for FedRAMP,  we recommend that CSPs explore the transition to OSCAL along with their FedRAMP R4 to R5 gap analysis and planning efforts. If you’re wondering about a FedRAMP R4 vs R5 gap analysis,  Rizkly, compliance automation software with dedicated FedRAMP OSCAL compliance experts, is ready to assist…just contact us.

    What’s the difference between CMMC and FedRAMP?2023-08-17T17:58:39+00:00

    By Chor-Ching Fan

    As organizations chart their growth through government contracts and assess the cost of cybersecurity compliance initiatives,  many wonder “what’s the the difference between CMMC and FedRAMP”?  The Cybersecurity Maturity Model Certification (CMMC) and the Federal Risk and Authorization Management Program (FedRAMP) are two different compliance frameworks that organizations must follow if they want to work with the US government.

    CMMC is a comprehensive framework designed to protect the defense industrial base’s (DIB) sensitive unclassified information.  While it started with five levels of maturity, the latest version of the CMMC 2.0 framework includes 3 levels and tracks very closely with the NIST 800-171 control framework.  All DoD contractors will need to achieve at least Level 1 (based on the sensitivity level of the information handled by the contractor) in order to keep and/or win new work with the DoD

    FedRAMP is a cybersecurity framework that focuses on the security of cloud service providers (CSPs) doing business with the US federal government. There are two approaches to achieving FedRAMP Authorization, a provisional authorization through the Joint Authorization Board (JAB) or an authorization through a specific government agency sponsor. The JAB is the primary governing body for FedRAMP and includes representation from the Department of Defense (DoD), Department of Homeland Security (DHS), and General Services Administration (GSA). There are four different control baselines that support the different FedRAMP authorization impact levels.

    CMMC FedRAMP
    Purpose Assesses and enhance the cybersecurity maturity of  all contractors working with the DoD Focuses on the security of cloud service providers serving federal agencies
    Certification/Authorization Levels 3 4
    Minimum Level Required for Work Contracts Level 1 (once CMMC is finalized) Authorized at applicable impact level
    Levels and Control Scope
    • CMMC Level 1: 15 controls
    • CMMC Level 2: 110 controls
    • CMMC Level 3: 134 controls
    • LI-SaaS (Low Impact SaaS): 37-57 controls
    • Low: 125 controls
    • Moderate: 325 controls
    • High impact: 421 controls
    Applicability Applies to all contractors that work with the DoD Applies to cloud service providers (CSPs) that work with US government agencies

    CMMC vs FedRAMP

    CSPs must achieve Authorized status in order to provide services to US government agencies.  Soon,  DoD contractors will need to achieve at least CMMC Level 1 status before winning new contracts.

    In general, FedRAMP is a more comprehensive framework than CMMC. FedRAMP requires organizations to enhance process maturity and capabilities across a wider range of topics dealing with data, network, staff, physical building and vendor security.  Here are additional considerations to keep in mind regarding CMMC and FedRAMP compliance:

    • CMMC has been in development for the past few years and is now (2023) nearing finalization.
    • FedRAMP is a mature framework (based on NIST 800-53) that has been in place for over a decade (2011).  We view it as the high bar for cloud cybersecurity compliance.
    • Both CMMC and FedRAMP are constantly evolving. The DoD, FedRAMP PMO and NIST are constantly updating the requirements to reflect the latest cybersecurity threats.
    • Compliance with CMMC and FedRAMP can be a complex and expensive process, especially for SMBs.  Rizkly helps SMBs consider their needs and regulatory requirements and offers an effective and efficient solution for achieving and sustaining improved cybersecurity posture and compliance.
    Do you perform system remediation work?2022-05-19T02:00:44+00:00

    Rizkly experts will advise, guide and review hardware and software technology changes to ensure that they address specific compliance controls but we do not perform the actual implementation work.  Over the years, we have a developed a trusted ecosystem of partners who offer effective and affordable solutions to expedite remediation of security and compliance gaps.  We will gladly refer you to appropriate partners if and when the need arises.   Creating policies,  procedures and other artifacts are also a key part of compliance remediation efforts and these are activities that our advisors do perform using powerful Rizkly features for policies and procedures.

    A description of the services that Rizkly expert advisors provide?2022-05-19T01:37:42+00:00

    Rizkly cybersecurity compliance advisors will work with you through the entire lifecycle of your compliance initiative.  We will scale up/down depending on specific need, and we co-create our involvement in the early stages of the project.  Typical project activities include:

    • Gain an understanding of your business, your clients, your system(s), and your anticipated compliance requirements
    • Educate your team members on compliance requirements, how to leverage the Rizkly app and what will be expected throughout the effort 
    • Develop the system ‘boundary’, and what will be in scope for compliance purposes
    • Draft a system architecture diagram that clearly depicts the system boundary
    • Review existing documentation and work with your team members to understand system and process specifics
    • Perform a high level gap assessment to determine what controls are in place and operating effectively, and where there are gaps
    • For each gap determine a detailed plan of action to remediate
    • Collaborate as needed with personnel (staff and/or your vendors) during remediation. 
    • Provide advisory support, develop documentation, design controls, review evidence, audit prep, etc.
    • Ensure that all artifacts and control implementation statements are effectively captured in Rizkly
    • Educate your team on how to leverage Rizkly to generate audit-ready documentation such as SSPs, POAM reports and SPRS scoring
    • Post-remediation ensure that all controls are in place and operating effectively

    Title

    Go to Top