Skip to main content

Summary: NIST SP 800-64 Rev 2


Although there may be numerous methodologies available today for developing software whether it is based on a sequential, prototyping or even iterative model, the absence of security at each phase will render applications being vulnerable and easily exploitable when deployed. NIST 800-64 Rev. 2 provides a guide that incorporates security into a sequential model of a SDLC. Currently, at my organization this type of model is preferred since there are small development teams.
One of the first recommendations made by is NIST 800-64 Rev. 2 is based on policy and guidelines. It states that there should be a written SDLC policy tailored to suit whether the business develops its own software or outsources software development and even maintenance. At my organization, there is a mesh of both. Large complex enterprise systems are usually outsourced while smaller manageable applications are developed in-house where there may not be an alternative available at a low cost. For example, human resources and student information management systems are purchased from large corporations like Oracle.

At the initiation phase, the business requirements in relation to maintaining the CIA triad, privacy and even business regulation requirements are outlined. In addition, it includes security planning, categorizing the information system, assessing the business and privacy impact and ensuring secure development processes. Next, in the development phase tasks include assessing risk, selecting security controls, designing the security architecture, developing security documentation and conducting testing. The third step, is the implementation phase, where the integration of security into production environment is done, system assessment and authorization is executed. At the operations and maintenance phase, security team must ensure the operational readiness is reviewed, configuration management and continuous monitoring.  When the information system is no longer in use, the disposal phase is executed which includes: following a transition plan, preserving information, sanitizing media, disposing of hardware and closing off the system. 

Comments

  1. I appreciate your succinct summary. While I understand that there is a lot more to it than just the information provided here, you've done well summarizing all of the main key-points in the SP. Thanks for doing so!

    ReplyDelete

Post a Comment

Popular posts from this blog

Summary: NIST SP 800-61 Rev 2

On another note, with respect to incident response management, the purpose is to provide a plan for a clear path of resolving a security breach. According to the Special Publication NIST 800-61 Rev. 2, the first thing that an organization should do is establish a clear organizational meaning of the word “incident”. It provides a guide to incident handling and recommends establishing response capabilities, incident response policies, an IR plan, procedures, information sharing mechanisms, team structure and even collaboration with external groups. The team’s structure, the services they provide along with the policies and procedures are established. This team consists of: internet service providers, incident reporters, law enforcement agencies, software and support vendors, customers and media as well as other teams. The recommended incident handling procedure consists of: preparation, detection and analysis, containment, eradication and recovery. During the preparation phase, the s...

Software Defined Networks: An Introduction

Description of the technology (Urias, Stout, & Loverro, 2015) Software defined networks (SDNs) is an emerging technology that is changing the defense and networking paradigm. (Hande, Jadhav, Patil, & Zagade, n.d.) Traditionally, network devices like switches and routers, using protocols (on the control plane) such as Open Shortest Path First(OSPF), Border Gateway Protocol(BGP) and Spanning Tree Protocol(STP) determine the best port or interface to forward packets (on the data plane). These routing protocols use static information such as hop count to determine the best path through the network. Moreover, (Ali, Sivaraman, Radford, & Jha, 2015) this decentralized method of network management is the leading cause of network faults and bugs due to errors during configuration. Not to mention, a proliferation of ’internet ossification phenomenon’ which is basically the stagnated network innovation. Additionally, there was no segregation of control and data plane which is har...