About Us | Contact Us
View Cart

Security in a Cloud Computing Environment

By Adam Reynolds | Tuesday, June 16, 2020 - Leave a Comment

An Update to the FFIEC Outsourced Cloud Computing Document


Cloud Computing graphic

In April 2020, the FFIEC released their “Joint Statement on Risk Management for Cloud Computing Services” as an update to their 2012 statement “Outsourced Cloud Computing.” The 2012 statement was a short, four-page document that addressed the key elements of outsourced cloud computing as identified in existing guidance. In 2012, the FFIEC considered cloud computing services as just another form of outsourcing “with the same basic risk characteristics and risk management requirements as traditional forms of outsourcing.” While outsourced cloud computing still shares the basic risks as traditional outsourcing, the 2020 statement provides examples of risk management practices that are relevant and unique to this form of outsourcing. These key risk management practices should be reviewed and used by management when assessing, implementing, and monitoring outsourced cloud computing services.

In properly assessing an outsourced service, one must first be aware of the risks. The documents help to understand the basic risks of outsourcing, as well as those that are pertinent to cloud computing services. To begin with, careful due diligence and review of contracts is a must. The relationship between the Client and provider must fully be understood, as well as the risks and controls that address them. The responsibilities for assessing and implementing controls over the operation must be known, as many security controls rely on proper understanding and implementation by the administrator. It is also important to understand the data classification of any information transmitted, stored, or processed in the cloud and how that data is segregated. Business continuity plans and recoverability of data should also be assessed to make sure it falls in line with the institution’s requirements and risk tolerances. Additionally, the institution’s incident response plan should carefully delineate the responsibilities of each party and account for the specific challenges that cloud resources present (which can often be found when including cloud services in incident response tests).

Implementation of cloud computing services present many unique considerations as outlined in the 2020 document, but also many typical ones as well. Awareness and training are a key control to effectively implement and monitor many controls, and this hold true for cloud computing as well. Proper change management controls are important for safely and effectively transitioning data and systems to cloud environments. A robust inventory process should also be in place to help facilitate other key processes such as secure configuration management and vulnerability management, as misconfiguration of cloud resources and unpatched applications are a common source of vulnerabilities in this environment.

Monitoring and oversight of cloud services is as critical of a practice as ever to ensure information is properly protected and the provider is meeting their contractual obligations. Regular testing and auditing of security controls and configurations to confirm that controls are properly configured, and working is one of the most important processes for security. Technical, administrative, and physical security controls protecting information assets should also be evaluated and monitored as shown in the documents, through items such as independent assurance reviews, reviewing security and activity reports from the cloud service provider, or other activities.

Outsourcing to cloud providers can provide many advantaged to your institution, but the additional risks should be thoroughly understood throughout the processes of assessment, implementation, and monitoring. The 2012 and 2020 joint statements highlight the existing guidance pertinent to cloud services as well provide examples of risk management practices for assessing risks and implementing controls in a cloud environment. Management should read both of these statements and compare their current policies and procedures against them to confirm compliance with guidance and to understand the risks and controls involved, helping to ensure a safe and effective use of cloud services.


Original article by Adam Reynolds, Senior Staff Auditor, infotex


same_strip_012513


 

Latest News
    Another awareness poster for YOUR customers (and users).  Now that we have our own employees aware, maybe it’s time to start posting content for our customers! Download the large versions here: Awareness Poster (Portrait) Awareness Poster (Landscape)   You are welcome to print out and distribute this around your office. Interested in one of ours […]
    Questions about China’s new disclosure laws only highlight the uncertainty about disclosure in general… An article review. China recently made waves in the security world by announcing a new set of data security laws, one of which has added new fuel to a long running debate: how and when should security vulnerabilities be disclosed…and to […]
    Four Conditions … …For Why a Network Can be Anything But a Network! Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . . I have to admit that infotex is being called into engineering meetings with larger organizations these days that are NOT community based banks.  We […]
    Another awareness poster for YOUR customers (and users).  Now that we have our own employees aware, maybe it’s time to start posting content for our customers! Download the large versions here: Awareness Poster (Portrait) Awareness Poster (Landscape)   You are welcome to print out and distribute this around your office. Interested in one of ours […]
    If Zero days need Zero clicks, are there any secure devices in the mix? Tanvee Dhir explores the Pegasus spyware. Another technical post, meant to inspire thought about IT Governance . . . . Introduction Over the past couple of weeks, we have seen multiple stories regarding a powerful piece of spyware called Pegasus sold […]
    Our Lead Non-Technical Auditor takes a look at the new AIO Guidance… Architecture, Infrastructure, and Operations (AIO) is the latest booklet released by the Federal Financial Institutions Examination Council (FFIEC) in their line of  IT Examination Handbooks. It is an update to their 2004 Operations booklet and, as the name implies, expands into the areas […]
    Another awareness poster for YOUR customers (and users).  Now that we have our own employees aware, maybe it’s time to start posting content for our customers! Download the large versions here: Awareness Poster (Portrait) Awareness Poster (Landscape)   You are welcome to print out and distribute this around your office. Interested in one of ours […]
    Many organizations still fail to consider the unique risks posed by cloud computing… An article review. Last month thousands of Western Digital MyCloud device owners learned about the risks of cloud-based solutions the hard way: their data had been wiped remotely due to a flaw in the internet-facing component of their external hard drives. While […]
    infotex does not use Kaseya… We are protecting our Clients! Another blog post meant to inspire thought about IT Governance . . . . To all infotex managed security service Clients: As you may be aware there was a large ransomware attack recently that leveraged a remote management tool called Kaseya that is used by many […]
    While we’re not a news service, we often use current events to comment on trends and our services. This blog is intended to get people thinking about topics and trends in Technology Risk Management, through our article reviews, as well as through original blog articles about current events and our MSSP services (such as our […]