Don’t be a Dummy – FTC Warns against Inadequate Security Controls in “Dummy” (Non-Production) Environments

by Polsinelli
Contact

The FTC recently announced a revised settlement with Uber Technologies, Inc. (“Uber”) in which the ride-sharing company has agreed to expand the proposed settlement it reached with the FTC last year over charges that Uber deceived consumers about its privacy and data security practices.  The revised settlement took into account a 2016 breach of customer data that Uber failed to disclose during the August 2017 settlement.  According to the complaint, Uber software engineers developed and tested software that had connectivity to cloud data using inadequate access controls.  In November 2016 Uber learned that hackers exploited this vulnerability in order to gain full access to Uber’s cloud storage environment, which contained unencrypted data files with more than 25 million names and email addresses, 22 million names and mobile phone numbers, and 600,000 names and driver’s license numbers of U.S. Uber drivers and riders.    

Although production environments typically receive the most attention from an information security perspective, the Uber settlement highlights the risks of failing to properly secure non-production environments utilized for development, testing, and quality assurance purposes. Neil Chilson, Chief Technologist of the FTC, explains “Insecure non-production environments leave a company open to corporate espionage, sabotage by competitors, and yes, theft of private consumer data.”  In short, non-production environments traditionally have weak security controls and hackers know it.  With more than 80% of companies reporting they use sensitive production data for non-production activities, there is a critical need to better understand the challenges of securing these environments and potential solutions for doing so:   

Securing Non-Production Environments Presents Several Challenges:

1.  Demands of the Environment  

In order for non-production environments to achieve their intended purpose (provide a space that enables developers to freely write and test code), developers must have broad access to data and functionality, which frequently translates into imposing less formal security standards.  In addition, because software is still in the development phase, it may not embody all of the typical security features that would otherwise be incorporated into the production code.  Non-production environments instead are   typically governed by access controls so only authorized developers can access the environment.

2.  Use of “Dummy” Data

Many developers believe dummy data doesn’t serve as the best test data as the variances or error messages cannot be replicated to the same degree of precision as would be the result when “real” client data is used.  Actual client data could contain personally identifiable information or other sensitive information that if disclosed in an unauthorized manner, could result in liability for vendors under various laws and regulations. 

3.  Incorporation of Security Standards

Pressure to meet tight client deadlines may result in a rushed transition from non-production to production environments.  As a result, the incorporation of security elements that were not present during the development stage can be missed.

Tips to Protect Non-Production Environments:     

1.  Data usage within non-production environments should be governed by enterprise level data governance policies and procedures, including limiting data usage to that which is only absolutely necessary (i.e., if personally identifiable information or other sensitive data elements aren’t required, remove them from test data in order to mitigate risk). 

2.  Emphasize the importance of utilizing data security practices regardless of the stage of software development.  When possible, try to replicate production environment security control methods in non-production environments, otherwise seek security methods customizable for purposes of the non-production environment, such as data masking (method by which one-way algorithms are applied to the data enabling de-identification of specific elements within the set). 

3.  Re-enforce the importance of access controls (multi-factor authentication, VPN, etc.) and ensure they are being enforced.

4.  Make sure developers know that unless they are working on an open-source project, proprietary code shouldn’t go within public repositories (and if it is an open source project, code should be carefully reviewed prior to submission for purposes of removing any vulnerabilities, such as hardcoded keys and logins).

5.  If security features are removed from development features, have a process for accounting for these items prior to code being placed into production.

6.  Conduct protective monitoring of the development environment to determine if the environment is subject to unauthorized activity – (i.e., strange websites being accessed).

7.  Include data governance and information security obligations as it relates to non-production environments as part of internal audit processes to ensure proper protocol is being followed.

 

DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© Polsinelli | Attorney Advertising

Written by:

Polsinelli
Contact
more
less

Polsinelli on:

Readers' Choice 2017
Reporters on Deadline

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
Sign up using*

Already signed up? Log in here

*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Custom Email Digest
Privacy Policy (Updated: October 8, 2015):
hide

JD Supra provides users with access to its legal industry publishing services (the "Service") through its website (the "Website") as well as through other sources. Our policies with regard to data collection and use of personal information of users of the Service, regardless of the manner in which users access the Service, and visitors to the Website are set forth in this statement ("Policy"). By using the Service, you signify your acceptance of this Policy.

Information Collection and Use by JD Supra

JD Supra collects users' names, companies, titles, e-mail address and industry. JD Supra also tracks the pages that users visit, logs IP addresses and aggregates non-personally identifiable user data and browser type. This data is gathered using cookies and other technologies.

The information and data collected is used to authenticate users and to send notifications relating to the Service, including email alerts to which users have subscribed; to manage the Service and Website, to improve the Service and to customize the user's experience. This information is also provided to the authors of the content to give them insight into their readership and help them to improve their content, so that it is most useful for our users.

JD Supra does not sell, rent or otherwise provide your details to third parties, other than to the authors of the content on JD Supra.

If you prefer not to enable cookies, you may change your browser settings to disable cookies; however, please note that rejecting cookies while visiting the Website may result in certain parts of the Website not operating correctly or as efficiently as if cookies were allowed.

Email Choice/Opt-out

Users who opt in to receive emails may choose to no longer receive e-mail updates and newsletters by selecting the "opt-out of future email" option in the email they receive from JD Supra or in their JD Supra account management screen.

Security

JD Supra takes reasonable precautions to insure that user information is kept private. We restrict access to user information to those individuals who reasonably need access to perform their job functions, such as our third party email service, customer service personnel and technical staff. However, please note that no method of transmitting or storing data is completely secure and we cannot guarantee the security of user information. Unauthorized entry or use, hardware or software failure, and other factors may compromise the security of user information at any time.

If you have reason to believe that your interaction with us is no longer secure, you must immediately notify us of the problem by contacting us at info@jdsupra.com. In the unlikely event that we believe that the security of your user information in our possession or control may have been compromised, we may seek to notify you of that development and, if so, will endeavor to do so as promptly as practicable under the circumstances.

Sharing and Disclosure of Information JD Supra Collects

Except as otherwise described in this privacy statement, JD Supra will not disclose personal information to any third party unless we believe that disclosure is necessary to: (1) comply with applicable laws; (2) respond to governmental inquiries or requests; (3) comply with valid legal process; (4) protect the rights, privacy, safety or property of JD Supra, users of the Service, Website visitors or the public; (5) permit us to pursue available remedies or limit the damages that we may sustain; and (6) enforce our Terms & Conditions of Use.

In the event there is a change in the corporate structure of JD Supra such as, but not limited to, merger, consolidation, sale, liquidation or transfer of substantial assets, JD Supra may, in its sole discretion, transfer, sell or assign information collected on and through the Service to one or more affiliated or unaffiliated third parties.

Links to Other Websites

This Website and the Service may contain links to other websites. The operator of such other websites may collect information about you, including through cookies or other technologies. If you are using the Service through the Website and link to another site, you will leave the Website and this Policy will not apply to your use of and activity on those other sites. We encourage you to read the legal notices posted on those sites, including their privacy policies. We shall have no responsibility or liability for your visitation to, and the data collection and use practices of, such other sites. This Policy applies solely to the information collected in connection with your use of this Website and does not apply to any practices conducted offline or in connection with any other websites.

Changes in Our Privacy Policy

We reserve the right to change this Policy at any time. Please refer to the date at the top of this page to determine when this Policy was last revised. Any changes to our privacy policy will become effective upon posting of the revised policy on the Website. By continuing to use the Service or Website following such changes, you will be deemed to have agreed to such changes. If you do not agree with the terms of this Policy, as it may be amended from time to time, in whole or part, please do not continue using the Service or the Website.

Contacting JD Supra

If you have any questions about this privacy statement, the practices of this site, your dealings with this Web site, or if you would like to change any of the information you have provided to us, please contact us at: info@jdsupra.com.

- hide
*With LinkedIn, you don't need to create a separate login to manage your free JD Supra account, and we can make suggestions based on your needs and interests. We will not post anything on LinkedIn in your name. Or, sign up using your email address.