CDC Home
Help

Project Management Newsletter



Security Issues that Project Managers at CDC Need to Address

Newsletter Archive
Click Here to Subscribe

Volume 2 | Issue 5 | June 2008

Daniel Vitek, MBA, PMP

Almost all projects use, or produce, some form of information technology and/or information. More often than not, this information needs to be protected through some form of security. Security planning is an integral part of the overall project life cycle and incorporates many different aspects to be considered when planning a project. However, ultimately what is being protected is the data produced by the system, the information that data is used to create, and in some instances, the decisions made based upon that information.

A security threat is something that jeopardizes the confidentiality, integrity, and/or availability of a system’s data. Security risks result from such threats. Planning to address such items begins in the very early stages of a project’s life with the identification of these security related threats and risks. Subsequent efforts work towards continually identifying new threats and minimizing identified security risks through the diligent planning and execution of risk mitigation strategies specifically developed to address each unique threat.

Security of information and associated information technology systems must to be considered when planning projects, developing applications, implementing systems, etc. To be effective, security must be planned for and designed into a system from the very beginning, reviewed periodically during the life of the project, and be maintained throughout the life of the system. As a result, planning early and incorporating security into all phases of a project’s life cycle is often considerably easier and much less expensive than waiting until later project phases to consider it.

When considering the security of information systems, it can be decomposed in three main components that require consideration; hardware, software, and communications. Planning for how each of these areas is protected involves not only consideration of people, policy, practice, etc. but also budgetary considerations to provide for the review of they system, resource requirements, implementation of security solutions, ongoing security maintenance, etc.

The image to the right illustrates the ultimate goal of such efforts which is to support the confidentiality, integrity, and availability of system data.
In the center of the image are the data and/or services that the security planning effort is attempting to protect. An information system has:

  • Confidentiality - disclosure or exposure to unauthorized individuals or systems is prevented
  • Integrity - data cannot be created, changed, or deleted without proper authorization
  • Availability - information and the security controls used to protect it are functioning correctly when the information is needed

Items to avoid that will strengthen the security of a system and/or the information it produces include:

  • Avoid designing and writing poor applications
  • Perform regular system security assessments
  • Use server side certificates (SSL)
  • Hash passwords and encrypt sensitive data
  • Utilize access control management, role based authentication, that grants only the minimum privileges required for what users need to do
  • Do not mix sensitive and non-sensitive data
  • Change default admin passwords
  • Ensure the system is backed-up and encrypted
  • Separate development, staging, and testing environments from production environments
  • Do not use production data in a development environment
  • Train users, developers, DBA’s, etc. on security policies, procedures, etc.

To ensure proper security all CDC information systems are certified and accredited (C&A) based on the standards defined in NIST SP 800-37, Guide for the Security Certification and Accreditation of Federal Information Systems. The CDC C&A process ensures that information systems are:

  • Operating with appropriate management review
  • Performing ongoing security control monitoring
  • Submitted for reaccreditations before the end of the accreditation period (at least every 3 years) or when significant change to an information system or its environment has occurred

CDC’s C&A process also involves making recommendations to enhance existing system security controls, and to implement additional security controls to mitigate system vulnerabilities discovered while conducting a risk assessment. Additional information on this and other security related items can be found on the Office of the Chief Information Security Officer (OCISO) website located on the CDC intranet.

    

CDC Unified Process Working on HHS EPLC

The Department of Health and Human Services (HHS) Enterprise Performance Life Cycle (EPLC) Framework will provide HHS with a solid project management methodology that incorporates best government, and commercial, practices through a consistent and repeatable process, and provides a standard structure for planning, managing, and overseeing projects over their entire life cycle.

To successfully deliver the EPLC Framework, and its supporting project management artifacts, HHS is utilizing a collaborative development approach that allows all HHS operating divisions (OPDIV) to contribute to the development of EPLC artifacts. HHS has challenged the CDC, and other HHS OPDIV, by proposing an aggressive deadline for delivery of such artifacts. Scheduled are over one hundred artifacts to be created, critiqued, and finalized over the next few months. To successfully deliver on this challenge, HHS has requested that the CDC Unified Process (UP) Team take a lead role in the planning, facilitation, development, and delivery of this effort.

The CDC UP Team, in collaboration with HHS, and other HHS OPDIVs, have been aggressively working on the EPLC for several weeks and will be doing so for several more. The CDC UP Design Group has been an integral part of this effort. Made up of representatives from across the CDC the Design Group acts as CDC’s voice in the EPLC development effort. Working collaboratively and utilizing technology to assist the process, the CDC UP Design Group has been meeting weekly to review new draft EPLC artifacts, share ideas, discuss points of interest, and make suggestions to HHS regarding final development of HHS EPLC artifacts.

For more information and tools related to the topic(s) covered in this newsletter, the CDC Unified Process, or the Project Management Community of Practice please visit the CDC Unified Process website at http://www.cdc.gov/cdcup/.

Please also visit the CDC Unified Process Newsletter Archive located at http://www2.cdc.gov/cdcup/library/newsletter/ for access to many additional newsletters, articles, and management related topics and information.
  

CDC UNIFIED PROCESS PRESENTATIONS

The CDC UP offers a short overview presentation to any CDC FTE or Non-FTE group. Presentations are often performed at your location, on a day of the week convenient for your group, and typically take place over lunch structured as one hour lunch-and-learn style meeting.

Contact the CDC Unified Process at cdcup@cdc.gov or visit http://www.cdc.gov/cdcup/ to arrange a short overview presentation for your group.

CONTACT THE CDC UNIFIED PROCESS 

The CDC Unified Process Project Management Newsletter is authored by Daniel Vitek, MBA, PMP and published by the Office of Surveillance, Epidemiology, and Laboratory Services.

For questions about the CDC Unified Process, comments regarding this newsletter, suggestions for future newsletter topics, or to subscribe to the CDC Unified Process Project Management Newsletter please contact the CDC Unified Process atcdcup@cdc.gov or visithttp://www.cdc.gov/cdcup/

    

PROJECT MANAGEMENT COMMUNITY OF PRACTICE

  • January 25, 2008
    Topic: CDC IR Governance and Health and human Services Enterprise Performance Life Cycle
  • February 29, 2008
    Topic: Project Server
  • March 28, 2008
    Topic: Mid Tier Data center and Designated Server Site
  • April 25, 2008
    Topic: Program Management Professional Certification
  • May 16, 2008
    Topic: Security Issues that a Project Manager at CDC Needs to Address
  • June 27, 2008
    Topic: Procurement and Grants Office Processes
  • July 24, 2008
    Topic: Project Management Career Framework
  • August 22, 2008
    Topic: General Management vs. Project Management
  • September 26, 2008
    Topic: Records Management, Privacy Impact Analysis, and Classified Information
  • October 24, 2008
    Topic: Facilitation - A Key to Project Success
  • December 05, 2008
    Topic: Influence - A Critical Skill for Successful Project Managers



 

Add This Socialize the CDC Unified Process:

USA.gov: The U.S. Government's Official Web PortalDepartment of Health and Human Services
Centers for Disease Control and Prevention   1600 Clifton Rd. Atlanta, GA 30333, USA
800-CDC-INFO (800-232-4636) TTY: (888) 232-6348, 24 Hours/Every Day - cdcinfo@cdc.gov

A-Z Index

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
  7. G
  8. H
  9. I
  10. J
  11. K
  12. L
  13. M
  14. N
  15. O
  16. P
  17. Q
  18. R
  19. S
  20. T
  21. U
  22. V
  23. W
  24. X
  25. Y
  26. Z
  27. #