DOCSLIB.ORG

The Tips and Tricks Guide to Software Security Assurance, Volumes 1& 2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

TTipsips andand TTricksricks GuideGuidetm TToo Software Security Assurance Kevin Beaver Introduction Introduction to Realtimepublishers by Sean Daily, Series Editor The book you are about to enjoy represents an entirely new modality of publishing and a major first in the industry. The founding concept behind Realtimepublishers.com is the idea of providing readers with high-quality books about today’s most critical technology topics—at no cost to the reader. Although this feat may sound difficult to achieve, it is made possible through the vision and generosity of a corporate sponsor who agrees to bear the book’s production expenses and host the book on its Web site for the benefit of its Web site visitors. It should be pointed out that the free nature of these publications does not in any way diminish their quality. Without reservation, I can tell you that the book that you’re now reading is the equivalent of any similar printed book you might find at your local bookstore—with the notable exception that it won’t cost you $30 to $80. The Realtimepublishers publishing model also provides other significant benefits. For example, the electronic nature of this book makes activities such as chapter updates and additions or the release of a new edition possible in a far shorter timeframe than is the case with conventional printed books. Because we publish our titles in “real-time”—that is, as chapters are written or revised by the author—you benefit from receiving the information immediately rather than having to wait months or years to receive a complete product. Finally, I’d like to note that our books are by no means paid advertisements for the sponsor. Realtimepublishers is an independent publishing company and maintains, by written agreement with the sponsor, 100 percent editorial control over the content of our titles. It is my opinion that this system of content delivery not only is of immeasurable value to readers but also will hold a significant place in the future of publishing. As the founder of Realtimepublishers, my raison d’être is to create “dream team” projects—that is, to locate and work only with the industry’s leading authors and sponsors, and publish books that help readers do their everyday jobs. To that end, I encourage and welcome your feedback on this or any other book in the Realtimepublishers.com series. If you would like to submit a comment, question, or suggestion, please send an email to [email protected], leave feedback on our Web site at http://www.realtimepublishers.com, or call us at 800-509- 0532 ext. 110. Thanks for reading, and enjoy! Sean Daily Founder & Series Editor Realtimepublishers.com, Inc. i Table of Contents Note to Reader: This book presents tips and tricks for four software security topics. For ease of use, the questions and their solutions are divided into topics, and each question is numbered based on the topic, including • Topic 1: Managing for Software Security • Topic 2: Developing for Software Security • Topic 3: Auditing for Software Security • Topic 4: Testing for Software Security Introduction to Realtimepublishers.................................................................................................. i Topic 1: Managing for Software Security .......................................................................................1 Q 1.1: What software security-related problems exist in business today and what are the underlying causes?...........................................................................................................................1 The Root Cause....................................................................................................................1 Contributing Factors ............................................................................................................2 Q 1.2: What software is affected by poor quality and security vulnerabilities?..............................4 Q 1.3: As a software development manager, why should I be worried about reducing the number of vulnerabilities in the software my teams produce? .....................................................................5 Q 1.4: What are some tangible benefits of enhancing the security of our software? ......................6 Q 1.5: What can I do to feel confident answering the common question “How do I know your software is secure?” .........................................................................................................................7 Q 1.6: Is there a solid security strategy I can implement to help ensure my teams build solid applications? ....................................................................................................................................8 Integration with the Software Development Life Cycle......................................................8 Establish Goals.....................................................................................................................9 Proven Strategies .................................................................................................................9 Q 1.7: With so many security technologies at our disposal, how it is possible that software is still being compromised and applications are still being attacked?......................................................10 Q 1.8: At what point in the development process should we focus our efforts in order to minimize software security vulnerabilities? ..................................................................................12 Q 1.9: Which software components and functions are plagued by the most security vulnerabilities and why? ................................................................................................................13 Q 1.10: As a business executive, why should I be worried about security problems with my company’s software? .....................................................................................................................14 Q 1.11: Are there specific areas I should be concerned with regarding the identification and removal of software security vulnerabilities that arise related to offshoring?...............................16 Q 1.12: Are there specific software security areas I should be concerned with or that might require a specific approach related to mergers and acquisitions?..................................................17 ii Table of Contents Topic 2: Developing for Software Security...................................................................................18 Q 2.1: Why should software developers be bothered with tacking on security as yet another task to have to worry about?..................................................................................................................18 Q 2.2: What key areas should our development team focus on to ensure the most solid and secure applications long term?..................................................................................................................19 Q 2.3: What are some commonly overlooked software security vulnerabilities? .........................20 Revealing Comments.........................................................................................................20 Buffer Overflows ...............................................................................................................20 Mishandling Passwords and Logins...................................................................................20 Assumption that Encrypting Data in Transit Means Everything Is Secure .......................21 Not Considering the Network or Operating System Layers ..............................................21 Q 2.4: How can software security vulnerabilities be categorized so they’re easier to understand?22 Denial of Service................................................................................................................22 Authentication Weaknesses ...............................................................................................22 Input Attacks......................................................................................................................23 Directory Traversals...........................................................................................................23 Improper Storage of Files and Data...................................................................................23 Q 2.5: Are there any common software development practices that stand out as serious risks?...24 Q 2.6: Are there other technologies or layered security measures we can integrate into our software to help prevent various attacks? ......................................................................................24 Q 2.7: What role does a layered security defense play in software development?........................25 Q 2.8: There is a general consensus in my development lab that as long as firewalls and Secure Sockets Layer (SSL) are used, the application is secure—is this true?.........................................27 Q 2.9: Do I have anything to worry about as long as I develop software with the Open Web Application Security Project (OWASP) Top 10 vulnerabilities in mind?.....................................27 Q 2.10: What development practices can we integrate into our daily development routines to reduce the number of security vulnerabilities? ..............................................................................29 Q 2.11: What development tools can we integrate into our daily development routines
Recommended publications
  • Vulnerability Assessment and Secure Coding Practices for Middleware Part 1

    Vulnerability Assessment and Secure Coding Practices for Middleware Part 1

    Vulnerability Assessment and Secure Coding Practices for Middleware Part 1 James A. Kupsch Computer Sciences Department University of Wisconsin © 2007-2008, James A. K1upsch. All rights reserved. Tutorial Objectives • Show how to perform the basics of a vulnerability assessment • Create more people doing vulnerability assessments • Show how different types of vulnerabilities arise in a system • Teach coding techniques that can prevent certain types of vulnerabilities • Make your software more secure 2 Roadmap • Part 1: Vulnerability Assessment Process – Introduction – Evaluation process – Architectural analysis – Computer process – Communication channels – Resource analysis – Privilege analysis – Data Flow Diagrams – Component analysis – Vulnerability Discovery Activities • Part 2: Secure Coding Practices 3 Security Problems Are Real Everyone with a computer knows this. If you’re not seeing vulnerability reports and fixes for a piece of software, it doesn’t mean that it is secure. It probably means the opposite; they aren’t looking or aren’t telling. The grid community has been largely lucky (security through obscurity). 4 Many Avenues of Attack We’re looking for attacks that exploit inherent weakness in your system. Internet Firewall: www server Attack web using www protocols Compromised host Internal bad guy 5 Impact of Vulnerabilities FBI estimates computer security incidents cost U.S. businesses $67 billion in 2005 [CNETnews.com] Number of reported vulnerabilities each year is increasing [CERT stats] 8000 6000 4000 2000 0 1994 1998
  • BEST PRACTICES in Anti-Terrorism Security for Sporting and Entertainment Venues RESOURCE GUIDE

    BEST PRACTICES in Anti-Terrorism Security for Sporting and Entertainment Venues RESOURCE GUIDE

    Command, Control and Interoperability Center for Advanced Data Analysis A Department of Homeland Security University Center of Excellence BEST PRACTICES in Anti-Terrorism Security for Sporting and Entertainment Venues RESOURCE GUIDE July 2013 Table of Contents Introduction to the Project ............................................................................................................7 Background...................................................................................................................................8 Identifying Best Practices in Anti-Terrorism Security in Sports Venues ......................................8 Identifying the Key Best Practices and Developing Metrics for Each .........................................11 Developing a Best Practices Resource Guide .............................................................................13 Testing the Guid e ........................................................................................................................13 Executive Summary....................................................................................................................13 Chapter 1 – Overview.................................................................................................................15 1.1 Introduction...........................................................................................................................15 1.2 Risk Assessment ...................................................................................................................15
  • A Study of Android Application Security

    A Study of Android Application Security

    A Study of Android Application Security William Enck, Damien Octeau, Patrick McDaniel, and Swarat Chaudhuri Systems and Internet Infrastructure Security Laboratory Department of Computer Science and Engineering The Pennsylvania State University enck, octeau, mcdaniel, swarat @cse.psu.edu { } Abstract ingly desire it, markets are not in a position to provide security in more than a superficial way [30]. The lack of The fluidity of application markets complicate smart- a common definition for security and the volume of ap- phone security. Although recent efforts have shed light plications ensures that some malicious, questionable, and on particular security issues, there remains little insight vulnerable applications will find their way to market. into broader security characteristics of smartphone ap- In this paper, we broadly characterize the security of plications. This paper seeks to better understand smart- applications in the Android Market. In contrast to past phone application security by studying 1,100 popular studies with narrower foci, e.g., [14, 12], we consider a free Android applications. We introduce the ded decom- breadth of concerns including both dangerous functional- piler, which recovers Android application source code ity and vulnerabilities, and apply a wide range of analysis directly from its installation image. We design and exe- techniques. In this, we make two primary contributions: cute a horizontal study of smartphone applications based on static analysis of 21 million lines of recovered code. We design and implement a Dalvik decompilier, • Our analysis uncovered pervasive use/misuse of person- ded. ded recovers an application’s Java source al/phone identifiers, and deep penetration of advertising solely from its installation image by inferring lost and analytics networks.
  • DDS Security Specification Will Have Limited Interoperability with Implementations That Do Implement the Mechanisms Introduced by This Specification

    DDS Security Specification Will Have Limited Interoperability with Implementations That Do Implement the Mechanisms Introduced by This Specification

    An OMG® DDS Security™ Publication DDS Security Version 1.1 OMG Document Number: formal/2018-04-01 Release Date: July 2018 Standard Document URL: https://www.omg.org/spec/DDS-SECURITY/1.1 Machine Consumable Files: Normative: https://www.omg.org/spec/DDS-SECURITY/20170901/dds_security_plugins_spis.idl https://www.omg.org/spec/DDS-SECURITY/20170901/omg_shared_ca_governance.xsd https://www.omg.org/spec/DDS-SECURITY/20170901/omg_shared_ca_permissions.xsd https://www.omg.org/spec/DDS-SECURITY/20170901/dds_security_plugins_model.xmi Non-normative: https://www.omg.org/spec/DDS-SECURITY/20170901/omg_shared_ca_governance_example.xml https://www.omg.org/spec/DDS-SECURITY/20170901/omg_shared_ca_permissions_example.xml Copyright © 2018, Object Management Group, Inc. Copyright © 2014-2017, PrismTech Group Ltd. Copyright © 2014-2017, Real-Time Innovations, Inc. Copyright © 2017, Twin Oaks Computing, Inc. Copyright © 2017, THALES USE OF SPECIFICATION – TERMS, CONDITIONS & NOTICES The material in this document details an Object Management Group specification in accordance with the terms, conditions and notices set forth below. This document does not represent a commitment to implement any portion of this specification in any company's products. The information contained in this document is subject to change without notice. LICENSES The companies listed above have granted to the Object Management Group, Inc. (OMG) a nonexclusive, royalty-free, paid up, worldwide license to copy and distribute this document and to modify this document and distribute copies of the modified version. Each of the copyright holders listed above has agreed that no person shall be deemed to have infringed the copyright in the included material of any such copyright holder by reason of having used the specification set forth herein or having conformed any computer software to the specification.
  • Opentext Product Security Assurance Program

    Opentext Product Security Assurance Program

    The Information Company ™ Product Security Assurance Program Contents Objective 03 Scope 03 Sources 03 Introduction 03 Concept and design 04 Development 05 Testing and quality assurance 07 Maintain and support 09 Partnership and responsibility 10 Privavy and Security Policy 11 Product Security Assurance Program 2/11 Objective The goals of the OpenText Product Security Assurance Program (PSAP) are to help ensure that all products, solutions, and services are designed, developed, and maintained with security in mind, and to provide OpenText customers with the assurance that their important assets and information are protected at all times. This document provides a general, public overview of the key aspects and components of the PSAP program. Scope The scope of the PSAP includes all software solutions designed and developed by OpenText and its subsidiaries. All OpenText employees are responsible to uphold and participate in this program. Sources The source of this overview document is the PSAP Standard Operating Procedure (SOP). This SOP is highly confidential in nature, for internal OpenText consumption only. This overview document represents the aspects that are able to be shared with OpenText customers and partners. Introduction OpenText is committed to the confidentiality, integrity, and availability of its customer information. OpenText believes that the foundation of a highly secure system is that the security is built in to the software from the initial stages of its concept, design, development, deployment, and beyond. In this respect,
  • The OWASP Application Security Program Quick Start Guide

    The OWASP Application Security Program Quick Start Guide

    Quick Start Guide The OWASP Application Security Program Quick Start Guide Five Days to Setting Up an Application Security Program Quickstart Guide About this Guide This guide is intended to be a short, straightforward introductory guide to standing-up or improving an Application Security Program1. The intended goal of the AppSec program is to implement measures throughout the code’s life- cycle to prevent gaps in the application security policy or the underlying system through flaws in the design, development, deployment, upgrade, or maintenance of the application. The application security program should effectively manage the security of its application systems, protecting information from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide integrity, confidentiality and availability. A fundamental component of this improved application security management is the ability to demonstrate acceptable levels of risk based on defined KPIs, including but limited to: 1. The number of vulnerabilities present in an application 2. The time to fix vulnerabilities 3. The remediation rate of vulnerabilities 4. The time vulnerabilities remain open The application security program deliverables include a holistic view of the state of security for each application, identifying the risks associated with the application and the countermeasures implemented to mitigate those risks, explaining how security is implemented, planning for system downtimes and emergencies, and providing a formal plan to improve the security in one or more of these areas. Audience The intended audience of this document is anyone from security engineers, developers, program managers, senior managers or a senior executive. This guide should be considered the start of a comprehensive approach, it is intended to give the basic questions and answers that should be asked by those who are in charge of the application security program in your organization, this includes those responsible for managing the risk of the entire organization.
  • Fedramp SECURITY ASSESSMENT FRAMEWORK

    Fedramp SECURITY ASSESSMENT FRAMEWORK

    FedRAMP SECURITY ASSESSMENT FRAMEWORK Version 2.4 November 15, 2017 EXECUTIVE SUMMARY This document describes a general Security Assessment Framework (SAF) for the Federal Risk and Authorization Management Program (FedRAMP). FedRAMP is a Government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud-based services. FedRAMP uses a “do once, use many times” framework that intends to save costs, time, and staff required to conduct redundant Agency security assessments and process monitoring reports. FedRAMP was developed in collaboration with the National Institute of Standards and Technology (NIST), the General Services Administration (GSA), the Department of Defense (DOD), and the Department of Homeland Security (DHS). Many other Government Agencies and working groups participated in reviewing and standardizing the controls, policies and procedures. | i DOCUMENT REVISION HISTORY DATE VERSION PAGE(S) DESCRIPTION AUTHOR Major revision for NIST SP 800-53 Revision 4. 06/06/2014 2.0 All FedRAMP PMO Includes new template and formatting changes. Formatting changes throughout. Clarified distinction 12/04/2015 2.1 All between 3PAO and IA. Replaced Figures 2 and 3, and FedRAMP PMO Appendix C Figures with current images. 06/06/2017 2.2 Cover Updated logo FedRAMP PMO Removed references to CSP Supplied Path to 11/06/2017 2.3 All Authorization and the Guide to Understanding FedRAMP PMO FedRAMP as they no longer exist. 11/15/2017 2.4 All Updated to the new template FedRAMP PMO HOW TO CONTACT US Questions about FedRAMP or this document should be directed to [email protected]. For more information about FedRAMP, visit the website at http://www.fedramp.gov.
  • Rogue Automation: Vulnerable and Malicious Code in Industrial

    Rogue Automation: Vulnerable and Malicious Code in Industrial

    In partnership with Rogue Automation Vulnerable and Malicious Code in Industrial Programming Federico Maggi Marcello Pogliani Trend Micro Research Politecnico di Milano Rogue Automation Vulnerable and Malicious Code in Industrial Programming Published by TREND MICRO LEGAL DISCLAIMER Trend Micro Research The information provided herein is for general information and educational purposes only. It is not intended and should not be construed to constitute legal advice. The information contained herein may not be applicable to all situations and may not reflect the most Written by current situation. Nothing contained herein should be relied on or acted upon without the benefit of legal advice based on the particular facts and circumstances presented and Federico Maggi nothing herein should be construed otherwise. Trend Micro reserves the right to modify Trend Micro Research the contents of this document at any time without prior notice. Marcello Pogliani Translations of any material into other languages are intended solely as a convenience. Politecnico di Milano Translation accuracy is not guaranteed nor implied. If any questions arise related to the accuracy of a translation, please refer to the original language official version of the document. Any discrepancies or differences created in the translation are not binding and With contributions from have no legal effect for compliance or enforcement purposes. Martino Vittone, Although Trend Micro uses reasonable efforts to include accurate and up-to-date Davide Quarta, information herein, Trend Micro makes no warranties or representations of any kind as to Stefano Zanero its accuracy, currency, or completeness. You agree that access to and use of and reliance Politecnico di Milano on this document and the content thereof is at your own risk.
  • Systems Administrator

    Systems Administrator

    SYSTEMS ADMINISTRATOR SUMMARY The System Administrator’s role is to manage in-house computer software systems, servers, storage devices and network connections to ensure high availability and security of the supported business applications. This individual also participates in the planning and implementation of policies and procedures to ensure system provisioning and maintenance that is consistent with company goals, industry best practices, and regulatory requirements. ESSENTIAL DUTIES AND RESPONSIBILITIES: The Authority’s Senior Systems Manager may designate various other activities. The following statements are intended to describe the general nature and level of work being performed. They are not intended to be construed, as an exhaustive list of all responsibilities, duties and skills required of personnel so classified. Nothing in this job description restricts management's right to assign or reassign duties and responsibilities to this job at any time for any reason, including reasonable accommodation. Operational Management Manage virtual and physical servers with Windows Server 2003 – 2012 R2 and RHEL operating systems Manage Active Directory, Microsoft Office 365, and server and workstation patching with SCCM Manage the physical and virtual environment (VMware) of 300 plus servers Have familiarity with MS SQL server, windows clustering, domain controller setup, and group policy Ensure the security of the server infrastructure by implementing industry best-practices regarding privacy, security, and regulatory compliance. Develop and maintain documentation about current environment setup, standard operating procedures, and best practices. Manage end user accounts, permissions, access rights, and storage allocations in accordance with best- practices Perform and test routine system backups and restores. Anticipate, mitigate, identify, troubleshoot, and correct hardware and software issues on servers, and workstations.
  • Web Application Vulnerabilities and Insecure Software Root Causes: the OWASP Top 10

    Web Application Vulnerabilities and Insecure Software Root Causes: the OWASP Top 10

    Vulnerability Analysis, Secure Development and Risk Management of Web 2.0 Applications Marco Morana OWASP OWASP Cincinnati Chapter, November 2010 Meeting Copyright © 2010 - The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License. The OWASP Foundation http://www.owasp.org What is OWASP? OWASP 2 Agenda For Today’s Presentation 1. The Evolution of Web 2.0 2. Web 2.0 Vulnerability Analysis 3. Building Secure Web 2.0 Applications 4. Web 2.0 Risk Management OWASP 3 The Evolution of the Internet to Web 2.0 OWASP 4 General Web 2.0 Background Can be defined as: “Web applications that facilitate interactive information sharing and collaboration, interoperability, and user-centered design on the World Wide Web” … the main characteristics of web 2.0 are: 1. Encourage user’s participation and collaboration through a virtual community of social networks/sites. Users can and add and update their own content, examples include Twitter and social networks such as Facebook, Myspace, LinkedIn, YouTube 2. Transcend from the technology/frameworks used AJAX, Adobe AIR, Flash, Flex, Dojo, Google Gears and others 3. Combine and aggregate data and functionality from different applications and systems, example include “mashups” as aggregators of client functionality provided by different in-house developed and/or third party services (e.g. web services, SaaS) OWASP 5 Web 2.0 As Evolution of Human Knowledge Source http://digigogy.blogspot.com/2009/02/digital-blooms-visual.html
  • Global Terrorism: IPI Blue Paper No. 4

    Global Terrorism: IPI Blue Paper No. 4

    IPI Blue Papers Global Terrorism Task Forces on Strengthening Multilateral Security Capacity No. 4 2009 INTERNATIONAL PEACE INSTITUTE Global Terrorism Global Terrorism Task Forces on Strengthening Multilateral Security Capacity IPI Blue Paper No. 4 Acknowledgements The International Peace Institute (IPI) owes a great debt of gratitude to its many donors to the program Coping with Crisis, Conflict, and Change. In particular, IPI is grateful to the governments of Belgium, Canada, Denmark, Finland, Greece, Luxembourg, the Netherlands, Norway, Spain, Sweden, Switzerland, and the United Kingdom. The Task Forces would also not have been possible without the leadership and intellectual contribution of their co-chairs, government representatives from Permanent Missions to the United Nations in New York, and expert moderators and contributors. IPI wishes to acknowledge the support of the Greentree Foundation, which generously allowed IPI the use of the Greentree Estate for plenary meetings of the Task Forces during 2008. note Meetings were held under the Chatham House Rule. Participants were invited in their personal capacity. This report is an IPI product. Its content does not necessarily represent the positions or opinions of individual Task Force participants. suggested citation: International Peace Institute, “Global Terrorism,” IPI Blue Paper No. 4, Task Forces on Strengthening Multilateral Security Capacity, New York, 2009. © by International Peace Institute, 2009 All Rights Reserved www.ipinst.org CONTENTS Foreword, Terje Rød-Larsen. vii Acronyms. x Executive Summary. 1 The Challenge for Multilateral Counterterrorism. .6 Ideas for Action. 18 I. strengThen Political SupporT For The un’S role In CounTerIng Terrorism ii. enhanCe straTegic CommunicationS iii. deePen relationShips BeTween un head- quarTerS and national and regIonal parTnerS Iv.
  • Cybersecurity in a Digital Era.Pdf

    Cybersecurity in a Digital Era.Pdf

    Digital McKinsey and Global Risk Practice Cybersecurity in a Digital Era June 2020 Introduction Even before the advent of a global pandemic, executive teams faced a challenging and dynamic environ- ment as they sought to protect their institutions from cyberattack, without degrading their ability to innovate and extract value from technology investments. CISOs and their partners in business and IT functions have had to think through how to protect increasingly valuable digital assets, how to assess threats related to an increasingly fraught geopolitical environment, how to meet increasingly stringent customer and regulatory expectations and how to navigate disruptions to existing cybersecurity models as companies adopt agile development and cloud computing. We believe there are five areas for CIOs, CISOs, CROs and other business leaders to address in particular: 1. Get a strategy in place that will activate the organization. Even more than in the past cybersecurity is a business issue – and cybersecurity effectiveness means action not only from the CISO organiza- tion, but also from application development, infrastructure, product development, customer care, finance, human resources, procurement and risk. A successful cybersecurity strategy supports the business, highlights the actions required from across the enterprise – and perhaps most importantly captures the imagination of the executive in how it can manage risk and also enable business innovation. 2. Create granular, analytic risk management capabilities. There will always be more vulnerabilities to address and more protections you can consider than you will have capacity to implement. Even companies with large and increasing cybersecurity budgets face constraints in how much change the organization can absorb.