Project #3: System Security Plan Company Background & Operating Environment The assigned case study and attachments to this assignment provide information about “the company.” Use the Baltimore field office as the target for the System Security Plan Use Verizon FiOS as the Internet Services Provider (see http://www.verizonenterprise.com/terms/us/products/internet/sla/ ) Policy Issue & Plan of Action A recent risk assessment highlighted the need to formalize the security measures required to protect information, information systems, and the information infrastructures for the company’s field offices. This requirement has been incorporated into the company’s risk management plan and the company’s CISO has been tasked with developing, documenting, and implementing the required security measures. The IT Governance board also has a role to play since it must review and approve all changes which affect IT systems under its purview. The CISO has proposed a plan of action which includes developing system security plans using guidance from NIST SP-800-18 Guide for Developing Security Plans for Federal Information Systems. The IT Governance board, after reviewing the CISO’s proposed plan of action, voted and accepted this recommendation. In its discussions prior to the vote, the CISO explained why the best practices information for security plans from NIST SP 800-18 was suitable for the company’s use. The board also accepted the CISO’s recommendation for creating a single System Security Plan for a General Support System since, in the CISO’s professional judgement, this type of plan would best meet the “formalization” requirement from the company’s recently adopted risk management strategy. Your Task Assignment As a staff member supporting the CISO, you have been asked to research and then draft the required system security plan for a General Support System. In your research so far, you have learned that: A general support system is defined as “an interconnected set of information resources under the same direct management control that shares common functionality.” (See NIST SP 800-18) The Field Office manager is the designated system owner for the IT support systems in his or her field office. The system boundaries for the field office General Support System have already been documented in the company’s enterprise architecture (see the case study). The security controls required for the field office IT systems have been documented in a security controls baseline (see the controls baseline attached to this assignment). Research: Review the information provided in the case study and in this assignment, especially the information about the field offices and the IT systems and networks used in their day to day business affairs. Review NIST’s guidance for developing a System Security Plan for a general support IT System. This information is presented in NIST SP 800-18. http://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-18r1.pdf Pay special attention to the Sample Information System Security Plan template provided in Appendix A. Review the definitions for IT Security control families as documented in Federal Information Processing Standard (FIPS) 200: Minimum Security Requirements for Federal Information and Information Systems (see section 3). Review the definitions for individual controls as listed in Appendix F Security Control Catalog in NIST SP 800-53 Security and Privacy Controls for Federal Information Systems and Organizations. http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf You should focus on those controls listed in the security controls baseline provided with this assignment. Write: Use the following guidance to complete the System Security Plan using the template from Appendix A of NIST SP 800-18. Sections 1 through 10 will contain information provided in the assigned case study. You may need to “interpret” that information when writing the descriptions. “Fill in the blanks” for information about the company or its managers which is not provided in the case study, i.e. names, email addresses, phone numbers, etc.). Make sure that your fictional information is consistent with information provided in the case study (name of company, locations, etc.). Section 11 should contain information about the field office’s Internet connection Do not include the table. Use the business Internet Services Provider listed at the top of this assignment file. Describe the system interconnection type in this section and service level agreement. Section 12 should contain information derived from the case study. You will need to identify the types of information processed in the field office and then list the laws and regulations which apply. For example, if the case study company processes or stores Protected Health Information, then this section must include information about HIPAA. If the company processes or stores credit card payment information, then this section must include information about the PCI-DSS requirements. Section 13 of the SSP will take the most editing time. Use the information about required security controls as provided security controls baseline. Create 3 sub sections (13.1 Management Controls, 13.2 Operational Controls, and 13.3 Technical Controls). You must provide a description for each category (see the definitions provided in Annex 11.B Minimum Security Controls in NIST SP 800-100 Information Security Handbook: A Guide for Managers). Using the information provided in the security controls baseline, place the required control families and controls under the correct sub section. Use the exact names and designators for the security control families and individual security controls. BUT, you MUST paraphrase any and all descriptions. Do NOT cut and paste from NIST documents. Section 14: use the due date for this assignment as the plan complete date. Section 15: leave the approval date blank. You will not have any other text in this section (since the plan is not yet approved). Use a professional format for your System Security Plan. Your document should be consistently formatted throughout and easy to read. Common phrases do not require citations. If there is doubt as to whether or not information requires attribution, provide a footnote with publication information or use APA format citations and references. You are expected to write grammatically correct English in every assignment that you submit for grading. Do not turn in any work without (a) using spell check, (b) using grammar check, (c) verifying that your punctuation is correct and (d) reviewing your work for correct word usage and correctly structured sentences and paragraphs. Submit For Grading Submit your System Security Plan in MS Word format (.docx or .doc file) for grading using your assignment folder. (Attach the file.) 1. Information System Name/Title: • Unique identifier and name given to the system. [use information from the case study] 2. Information System Categorization: • Identify the appropriate system categorization [use the information from the case study]. 3. Information System Owner: • Name, title, agency, address, email address, and phone number of person who owns the system. [Use the field office manager] 4. Authorizing Official: • Name, title, agency, address, email address, and phone number of the senior management official designated as the authorizing official. [Use the company’s Chief Information Officer.] 5. Other Designated Contacts: • List other key personnel, if applicable; include their title, address, email address, and phone number. [include the CISO, the ISSO, and other individuals from the case study, if appropriate] 6. Assignment of Security Responsibility: • Name, title, address, email address, and phone number of person who is responsible for the security of the system. [use the case study information] 7. Information System Operational Status: • Indicate the operational status of the system. If more than one status is selected, list which part of the system is covered under each status. [Use the case study information.] 8.0 Information System Type: • Indicate if the system is a major application or a general support system. If the system contains minor applications, list them in Section 9. General System Description/Purpose. [use the case study information] 9.0 General System Description/Purpose • Describe the function or purpose of the system and the information processes. [use the case study information] 10. System Environment • Provide a general description of the technical system. Include the primary hardware, software, and communications equipment. [use the case study information and diagrams. Add brand names, equipment types as required (if not provided in the case study)] 11. System Interconnections/Information Sharing • List interconnected systems and system identifiers (if appropriate), provide the system name, owning or providing organization, system type (major application or general support system) … add a fictional date of agreement to interconnect, and the name of the authorizing official. 12. Related Laws/Regulations/Policies • List any laws or regulations that establish specific requirements for the confidentiality, integrity, or availability of the data in the system. 13. Minimum Security Controls Use the security controls baseline as provided for this assignment. Include descriptive paragraphs for each section. Cut and paste the tables from the provided security controls baseline to add the individual security controls under each section. Use the sections and sub-sections as listed below. 13.1 Management Controls [provide a descriptive paragraph] 13.1.1 [first control family] [provide a descriptive paragraph] 13.1.2 [second control family] ………… 13.2 Operational Controls [provide a descriptive paragraph] 13.2.1 [first control family] 13.2.2 [second control family] ………….. 13.3 Technical Controls [provide a descriptive paragraph] 13.3.1 [ first control family] 13.3.2 [ second control family] ………… Example: 14. Information System Security Plan Completion Date: _____________________ • Enter the completion date of the plan. 15. Information System Security Plan Approval Date: _______________________ • Enter the date the system security plan was approved and indicate if the approval documentation is attached or on file.

    IT Pledge Plan coercion Baltimore Ground Station
    1. Counsel Scheme Name/Title:
    Red Clay Renovation’s Baltimore Ground Station
    2. Counsel Scheme Categorization:
    Moderate
    3. Counsel Scheme Owner:
    Name: Erica Kniesel
    Designation: Station Manager & ISSO
    Location: Baltimore Ground Station
    Agency: Red Clay Renovations
    Address: 200 Commerce Street
    Suite 450Baltimore, MD 21201
    Email: Erica@balt.redclayrenovations.com
    Phone: 443-555-2900
    4. Authorizing Official:
    Name: Erwin Carrington
    Designation: CIO & Director IT Employments
    Agency: Red Clay Renovations
    Address: 12209 Red Clay PlaceOwings Mills, MD 1117 Email: Erwin_Carrington@hq.redclayrenovations.com
    Phone: 667-555-6260
    5. Other Designated Contacts:
    Name:Eric Carpenter
    Designation: CISO / Deputy CIO
    Agency: Red Clay Renovations
    Address: 12209 Red Clay PlaceOwings Mills, MD 21117
    email: Eric_Carpenter@hq.redclayrenovations.com
    Phone: 667-555-6370

    Name: Charles Kniesel
    Designation: Manager &Architect inCharge
    Location: Baltimore ground StationBaltimore
    Phone:443-555-2900
    Email: Charles@balt.redclayrenovations.com
    6. Enactment of Pledge Responsibility:
    Name: Erica Kniesel
    Designation: Station Manager & ISSO
    Location: Baltimore Ground Station
    Agency: Red Clay Renovations
    Address: 200 Commerce Street
    Suite 450Baltimore, MD 21201
    Email: Erica@balt.redclayrenovations.com
    Phone: 443-555-2900

    7. Counsel Scheme Operational Status:
    Scheme Status is operational

    8.0 Counsel Scheme Type:
    General Support Scheme

    9.0 General Scheme Description/Purpose
    Red Clay renovation’s Baltimore station prepares “Internet of Things” and “Smprofession Home solutions, architectural frameworks, and designs. The network environment is then alike to the operations character at Red Clay Station via internet connectivity granted by Verizon FiOS. Constructive network connectivity links constructive stations and other ground sites to the deep operations character at the gathering station. Internal homogeneity is by wired and wireless connections.

    10. Scheme Environment
    100BASE-T Ethernet cable
    Alcatel Private Branch Exchange scheme
    Cat 5 cable
    CISCO Router
    CISCO Switch
    CISCO Wireless router
    Dell laptops and desktops (Windows 10 Enterprise)
    Dell servers (Windows server 2012)
    RJ-45 guidebearance jacks
    Symantec Endpoint Guard
    11. Scheme Homogeneitys/Counsel Sharing
    Transmission latency accelerate coercion Verizon’s’ regional hub routers that are set amid the United States borders is granted by Verizon FiOS, at an medium of 45 milliseconds. Accelerate coercion counsel and axioms being communicated counter the borders is plenteous slower averaging 90 milliseconds. Internet connectivity and national network employment gain be at space at integral times.

    12. Related Laws/Regulations/Policies
    Computer Fraud and Abuse Act of 1984
    Federal Counsel Modeing Standards Publication(FIPS) 199
    Federal Counsel Pledge Treatment Act of 2002
    Payment Card Industry Axioms Pledge Standard
    Sarbanes-Oxley, Identicality 404
    13. Minimum Pledge Guides

    Use the pledge guides baseline as granted coercion this enactment. Include described paragraphs coercion each identicality. Cut and paste the tables from the granted pledge guides baseline to infer the identical pledge guides beneath each identicality. Use the identicalitys and sub-sections as listed under.

    13.1 Treatment Guides

    The deep extrinsic of Treatment Guides id to ease and arrest axioms and counsel amid the counsel technology environment of the construction, focused on arrange treatment coercion immanent issues that may concern the scheme. Treatment guides families are as follows.

    13.1.1: Pledge Duty and Authorization
    Pledge duty guides gain scarcity to be created at Red Clay renovations as early as likely to fix to be talented to assess the usefulness if the scheme antecedent. Coercionmulate action plans coercion negotiation with vulnerabilities. Conduct an praise mode coercion integral participating devices and loose schemes. It is so expressive to warner the guides to fix that they prepare a penny and obvious scene of the scheme’s usefulness.

    13.1.2 Planning
    As per the pledge prudence, the construction shintegral coercionmulate exuberant pledge plans coercion its Counsel Technology environment. The plans prepare a obvious route map and scheme details as polite stipulations coercion fair experience of the scheme and construction’s internet connectivity runtime.
    PL-1
    Pledge Planning Prudence and Procedures
    PL-1
    PL-2
    Scheme Pledge Plan
    PL-2 (3)
    PL-4
    Rules of Behavior
    PL-4 (1)
    PL-8
    Counsel Pledge Architecture
    PL-8

    13.2 Operational Guides

    These are pledge protocols that are usually implemented by the counsel technology schemes by themselves outside the intercession of the user. They are polite elaborate and documented in the FIPS 200.

    13.2.1 Awareness and Inoculation Guides
    Fair and misapply awareness and inoculation programs gain be established (Wilson & Hash, 2003). These programs gain be aimed at ensuring that users are equipped with the lawful skills coercion interacting with the scheme. Counsel environing pledge arranges gain be granted and strong to whole workstation.
    AT-1
    Pledge Awareness and Inoculation Prudence and Procedures
    AT-1
    AT-2
    Pledge Awareness Inoculation
    AT-2 (2)
    AT-3
    Role-Based Pledge Inoculation
    AT-3
    AT-4
    Pledge Inoculation Records
    AT-4

    13.2.2 Contour treatment
    Contour treatment is the profession of ensuring that schemes pledge protocols are polite inferior in the mode of schemes engineering (Kloesterboer, 2007). It fixs that the contour tools coercion the scheme are polite accounted coercion as polite as facilitating homogeneity with the operational environment of the scheme.
    CM-1
    Contour Treatment Prudence and Procedures
    CM-1
    CM-2
    Baseline Contour
    CM-2 (1) (3) (7)
    CM-3
    Contour Change Guide
    CM-3 (2)
    CM-4
    Pledge Impact Analysis
    CM-4
    CM-5
    Advance Restrictions coercion Change
    CM-5
    CM-6
    Contour Settings
    CM-6
    CM-7
    Least Functionality
    CM-7 (1) (2) (4)
    CM-8
    Counsel Scheme Component Inventory
    CM-8 (1) (3) (5)
    CM-9
    Contour Treatment Plan
    CM-9
    CM-10
    Software Experience Restrictions
    CM-10

    13.3 Technical Guides

    These are pledge measures that are aimed at achieving the required guard standards coercion the scheme. The computer scheme may consummate these protocols by itself in an automated vestibule so that unacknowledged advance and prostitution of the scheme are poor level where there is no cosmical warrant to fix pledge. It so arranges exposure of unwanted exchange and supported pledge applications such as anti-virus protocols.

    13.3.1 Advance guides
    These are limitations to unacknowledged advance. They arrange the creation of password schemes. Encryptions, pursing and patching (Kuhn et al., 2010). They direct password extension and composition, biometrics and encrypting techniques. Most procedures are self-guard procedures.
    AC-1
    Advance Guide Prudence and Procedures
    AC-1
    AC-2
    Account Treatment
    AC-2 (1) (2) (3) (4)
    AC-3
    Advance Enforcement
    AC-3
    AC-4
    Counsel Flow Enforcement
    AC-4
    AC-5
    Separation of Duties
    AC-5
    AC-6
    Least Privilege
    AC-6 (1) (2) (5) (9) (10)
    AC-7
    Unsuccessful Logon Attempts
    AC-7
    AC-8
    Scheme Use Notification
    AC-8
    AC-11
    Session Lock
    AC-11 (1)
    AC-12
    Session Termination
    AC-12
    AC-14
    Permitted Actions outside Identification or Authentication
    AC-14

    13.3.2 Audit and Accountability
    These are pledge guides that fix the honor of the scheme they are aimed at warnering the scheme and ensuring it is running as per vocation requirements and that the secret counsel of the construction, as polite as vocation proceeding, are trustworthy. It so checks the experience of the scheme and helps propagate reports that are used coercion the judgment making mode.

    AU-1
    Audit and Accountability Prudence and Procedures
    AU-1
    AU-2
    Audit Levelts
    AU-2 (3)
    AU-3
    Content of Audit Records
    AU-3 (1)
    AU-4
    Audit Storage Space
    AU-4
    AU-5
    Response to Audit Modeing Failures
    AU-5
    AU-6
    Audit Review, Analysis, and Reporting
    AU-6 (1) (3)
    AU-7
    Audit Reduction and Report Generation
    AU-7 (1)
    AU-8
    Time Stamps
    AU-8 (1)
    AU-9
    Guard of Audit Counsel
    AU-9 (4)
    AU-10
    Non-repudiation
    Not Selected
    AU-11
    Audit Record Retention
    AU-11
    AU-12
    Audit Generation
    AU-12

    …………
    14. Counsel Scheme Pledge Plan Completion Date: ________29.11.2017_____________

    15. Counsel Scheme Pledge Plan Praise Date: _____29.11.2017__________________

    References
    Klosterboer, L. (2007). Implementing itil® contour treatment. IBM Press.
    Kuhn, D. R., Coyne, E. J., & Weil, T. R. (2010). Infering attributes to role-based advance guide. Computer, 43(6), 79-81.
    Wilson, M., & Hash, J. (2003). Building an counsel technology pledge awareness and inoculation program. NIST Special Publication, 800(50), 1-39.