Security Policies Group 1 - Week 8 policy for use of technology.

Slides:



Advertisements
Similar presentations
Protect Our Students Protect Ourselves
Advertisements

Surviving the PCI Self -Assessment James Placer, CISSP West Michigan Cisco Users Group Leadership Board.
Darton College Information Systems Use Policies. Introduction Dartons Information Systems are critical resources. The Information Systems Use Policies.
and Electronic Records Retention: IT Requirements Paul Dworak Office of Compliance
Identification and Disposition of Official University Records University of Texas at Arlington Records Management.
Annual Security Refresher Briefing Note: All classified markings contained within this presentation are for training purposes.
Information Security Policy
Section Six: Foreign Ownership, Control, or Influence (FOCI)
Information Security Policy
Information Systems Audit Program (cont.). PHYSICAL SECURITY CONTROLS.
Chapter 5: Asset Classification
ACG 6415 SPRING 2012 KRISTIN DONOVAN & BETH WILDMAN IT Security Frameworks.
Guide to Massachusetts Data Privacy Laws & Steps you can take towards Compliance.
Auditing Computer Systems
Information Security Awareness:
Information Security Policies and Standards
Lesson 11-Virtual Private Networks. Overview Define Virtual Private Networks (VPNs). Deploy User VPNs. Deploy Site VPNs. Understand standard VPN techniques.
ITS Offsite Workshop 2002 PolyU IT Security Policy PolyU IT/Computer Systems Security Policy (SSP) By Ken Chung Senior Computing Officer Information Technology.
Chapter 16 Security. 2 Chapter 16 - Objectives u The scope of database security. u Why database security is a serious concern for an organization. u The.
Chapter 9 Information Systems Controls for System Reliability— Part 2: Confidentiality and Privacy Copyright © 2012 Pearson Education, Inc. publishing.
Payment Card Industry (PCI) Data Security Standard
Section Three: Protection of Controlled Unclassified Information Note: All classified markings contained within this.
INTERNET and CODE OF CONDUCT
Session 3 – Information Security Policies
Presented by Manager, MIS.  GRIDCo’s intentions for publishing an Acceptable Use Policy are not to impose restrictions that are contrary to GRIDCo’s.
Section Ten: Security Violations and Deviations Note: All classified markings contained within this presentation are for training purposes only.
Teresa Macklin Information Security Officer 27 May, 2009 Campus-wide Information Security Activities.
CPS Acceptable Use Policy Day 2 – Technology Session.
Section Seven: Information Systems Security Note: All classified markings contained within this presentation are for training purposes only.
© 2012 IBM Corporation Rational Insight | Back to Basis Series Documents and Record Control Liu Xue Ning.
HIPAA PRIVACY AND SECURITY AWARENESS.
Information Systems Security Computer System Life Cycle Security.
Security Baseline. Definition A preliminary assessment of a newly implemented system Serves as a starting point to measure changes in configurations and.
Current Job Components Information Technology Department Network Systems Administration Telecommunications Database Design and Administration.
HQ Expectations of DOE Site IRBs Reporting Unanticipated Problems and Review/Approval of Projects that Use Personally Identifiable Information Libby White.
How Hospitals Protect Your Health Information. Your Health Information Privacy Rights You can ask to see or get a copy of your medical record and other.
Desktop computer security policies Applies to ALL computers connecting to the PathStone network irrespective of device ownership.
PRIVACY, SECURITY & ID THEFT PREVENTION - TIPS FOR THE VIGILANT BUSINESS - SMALL BUSINESS & ECONOMIC DEVELOPMENT FORUM October 21, WITH THANKS TO.
Information Systems Security
Lesson 9-Information Security Best Practices. Overview Understanding administrative security. Security project plans. Understanding technical security.
ACM 511 Introduction to Computer Networks. Computer Networks.
Information Asset Classification Community of Practicerev. 10/24/2007 Information Asset Classification What it means to employees.
The Culture of Healthcare Privacy, Confidentiality, and Security Lecture d This material (Comp2_Unit9d) was developed by Oregon Health and Science University,
Module 6: Designing Security for Network Hosts
 U.S. laws and their implemented regulations that prohibit the unauthorized “export” of certain controlled ITEMS, INFORMATION OR SOFTWARE to foreign.
Information Security IBK3IBV01 College 2 Paul J. Cornelisse.
ISO/IEC 27001:2013 Annex A.8 Asset management
International Security Management Standards. BS ISO/IEC 17799:2005 BS ISO/IEC 27001:2005 First edition – ISO/IEC 17799:2000 Second edition ISO/IEC 17799:2005.
Deck 10 Accounting Information Systems Romney and Steinbart Linda Batch March 2012.
Development of a Clean Room/Highly Restricted Zone June 12, 2012 Thomas Garrubba - CVS Caremark; Manager, Technical Assessments Group ©2011 The Shared.
TRUENORTH TECHNOLOGY POLICIES OVERVIEW. This includes but is not limited to : – Games – Non-work related software – Streaming media applications – Mobile.
Managing a “Data Spill”
ITACS L.L.P. Policy And Procedures Group 1. Objective: To establish companywide policy with regards to personal device usage both on and off of the company.
CIW Lesson 8 Part B. Malicious Software application that installs hidden services on systems term for software whose specific intent is to harm computer.
Computer Security Sample security policy Dr Alexei Vernitski.
By: Matt Winkeler.  PCI – Payment Card Industry  DSS – Data Security Standard  PAN – Primary Account Number.
Information Security Policy Development for Management By Peter McCarthy.
Security Methods and Practice Principles of Information Security, Fourth Edition CET4884 Planning for Security Ch5 Part I.
Blackboard Security System
Information Security Policy
MANAGEMENT of INFORMATION SECURITY, Fifth Edition
2016 Cybersecurity Law If any one of these describes your company
Module P6 Principle 6: Establish and Maintain a Management Process for Intellectual Property, Proprietary Information, and Competition-Sensitive Data Learning.
Chapter 3: IRS and FTC Data Security Rules
Confidentiality Agreement
HQ Expectations of DOE Site IRBs
Introduction to the PACS Security
Anatomy of a Common Cyber Attack
Presentation transcript:

Security Policies Group 1 - Week 8 policy for use of technology

Overview of Lockheed Martin Operations  Lockheed Martin (LM) provides solutions for “Aeronautics, Electronic Systems, Information Systems & Global Solutions, and Space Systems.” They utilize EASIstar  “External Access Secure Infrastructure (EASIstar) is a Lockheed Martin Information Systems & Global Solutions (IS&GS) Extranet” providing “customers, partners, teammates, subcontractors, and employees access to a virtual collaborative workspace with capabilities ranging from web access to application and file sharing all in a secure, reliable and cost -- effective manner”.

Information Security Policy Policy is a plan or course of action that influences and determine decisions.  EISP: Enterprise Information Security Policy sets the strategic direction, scope, and tone for all of an organization’s security efforts. assigns responsibilities for the various areas of information security. guides the development, implementation, and management requirements of the information security program.  ISSP: Issue Specific Security Policy Articulates the organization’s expectations about how the technology-based system in question should be used Documents how the technology-based system is controlled and identifies the processes and authorities that provide this control Serves to indemnify the organization against liability for an employee’s inappropriate or illegal system use  SysSP: System Specific Security Policy They are often created to function as standards or procedures to be used when configuring or maintaining systems. SysSPs can be separated into two general groups, management guidance and technical specifications

Parties Involved CISO of a medium sized IT company Contract for information exchange will use

Policy guidelines for use of EASIstar Requirements that are to be complied with when doing business with LM through EASIstar.

Lockheed Martin Information Assets Usage Policies Passwords

Virus Viruses and other malicious code pose a serious threat to Lockheed Martin users and customers. Virus prevention measures as guided by policy  virus protection software be installed and maintained on all Lockheed Martin managed, maintained or leased computing systems  all users of EASIstar must agree to acquire, install, utilize and maintain a current version of anti-virus software on any computer used to access the EASIstar Lockheed Martin Extranet  The following actions are strongly encouraged:  Virus signature files to be updated at lease every 7 days with the recommendation that virus signature files be installed within 24 hours of notification  Complete scans performed weekly  Virus Scan engine updates scheduled for at least once per month.  The downloading, installation, and/or use of freeware/shareware products on EASIstar assets is not permitted without prior Lockheed Martin Intellectual Property Law attorney approval.

Information Protection  Sensitive information (LM Proprietary Information, Third Party Proprietary, and Export Controlled) assets (data, systems, documentation, etc.) must be properly classified, labeled and protected. Data/Information owners are responsible for determining the sensitivity of all information to be electronically transmitted in accordance with these policies.  Protective Legends, Labels and other Markings. As appropriate, each item of Sensitive Information will bear a legend, label or other marking which serves to advise the holder that the information requires a specific degree of protection.  Export Controlled Information will be labeled as necessary to comply with the applicable US or foreign government laws and regulations and local procedures.  Lockheed Martin Proprietary Information will be labeled in accordance with approved labeling conventions.  Third Party Proprietary Information will be managed in accordance with the contractual arrangements under which it was received. Such information should not be accepted unless an appropriate written contractual arrangement, which establishes the requirements for protecting the information (e.g., a Proprietary Information Agreement), is in place between Lockheed Martin and the third party. Third Party Proprietary Information will bear the markings applied by the third party, and/or markings prescribed by the contract between Lockheed Martin and the third party. The markings will not be removed without authorization from the third party and/or cognizant Lockheed Martin Legal Counsel.

Disclosure  Lockheed Martin policies and the laws of the US and foreign governments impose specific requirements upon the disclosure of Sensitive Information. Failure to comply with these requirements is a violation of policy and may lead to a violation of law. Accordingly, the individual providing access to the Sensitive Information must take the following steps before any disclosure is made: Ensure that the Sensitive Information bears the legend, if any, as identified.  Determine the status of the intended recipient(s) (for example, whether he or she is an employee or a non-employee; a US Citizen or a Foreign Person). Obtain required documentation and approvals, if any, based upon this status (for example, a Proprietary Information Agreement or similar arrangement is required before LMPI is disclosed to a non- employee, and US government approval is required before Export Controlled Information is disclosed to a Foreign Person).

Other factors to consider  Transmission: Ensure that the selected transmittal method is secure and complies with this policy and the laws of the recipient country (for example, encryption is prohibited by some foreign countries)  Storage: When not in use, Sensitive Information in databases, desktop hard drives or local area networks will be protected by unique userID and password at a minimum.  Encryption is recommended for Sensitive Information stored in non-US locations, except where prohibited by law. Sensitive Information stored on an asset that is not controlled and managed by Lockheed Martin (e.g., a personally-owned computer) will be protected by unique userID and password at a minimum.  Disposition: Sensitive Information will be retained as required by law, regulation, contract, policy, or, if none of these applies, until no longer useful. Electronic information will be deleted or overwritten using overwriting software approved by Lockheed Martin Enterprise Information Systems. Overwriting is required if Sensitive Information will be disposed of in a non-US location

General usage  If a EASIstar Information Technology user suspects or has actual knowledge that the protection of Sensitive Information has been compromised in a manner that appears to be a violation of law, the individual must report such suspicion or actual knowledge to the appropriate Lockheed Martin EASIstar administrator  Ensure Assets connected to EASIstar systems are properly locked or otherwise protected when unattended (e.g., through use of a Power-on password, Password-secured screen saver, etc.)  Carefully Assess all received software or Information (for malicious code) before Execution or Storage  A Lockheed Martin policy prohibiting the use of split tunneling (i.e. simultaneous network access to two or more networks) is in effect when 1) connecting into EASIstar over a Virtual Private Network (VPN) connection, and 2) connecting out of EASIstar over a VPN connection to a remote network.

Reference