![Your role - 2 Obey Strong Authentication Policy (Kerberos) Don’t run network services (login or read write ftp) unless they demand Kerberos authentication Treat your kerberos password as a sacred object (never expose it over the network) Promptly report potential computer security incidents X2345 or [email_address] Follow FCIRT instructions during incidents (especially about keeping infected machines off the network and preserving the status of an infected machine for expert investigation)](https://image.slidesharecdn.com/basiccomputersecurity-110626230000-phpapp01/85/Basic-computersecurity-15-320.jpg)
![Questions? [email_address] [email_address] for questions about security policy [email_address] for reporting security incident http://computing.fnal.gov/security](https://image.slidesharecdn.com/basiccomputersecurity-110626230000-phpapp01/85/Basic-computersecurity-24-320.jpg)
Basic computersecurity
- 2. Outline Why Computer Security Fermilab Strategy: Integrated Computer Security Defense in Depth Your role and responsibilities as a user Other Computing Policy Issues Data backup Incidental use Privacy Offensive material Licensing
- 3. Why Computer Security The Internet is a dangerous place We are constantly being scanned for weak or vulnerable systems; new unpatched systems will be exploited within minutes. Fermilab is an attractive target High network bandwidth is useful for attackers who take over lab computers Publicity value of compromising a .gov site Attackers may not realize we have no information useful to them
- 4. Why Computer Security - 2 We need to protect Our data Our ability to use our computers (denial of service attacks) Our reputation with DOE, Congress and the general public Major sources of danger Running malicious code on your machine due to system or application vulnerabilities or improper user actions Carrying infected machines (laptops) in from off site
- 5. FNAL Strategy Integrated Security Management Defense in Depth Perimeter Controls and auto blocking Mail gateway virus scanning Strong Authentication (Kerberos) Critical System plans Critical vulnerabilities Prompt response to computer security incidents (FCIRT) Intelligent and informed user community
- 6. Integrated Security Management Computer Security is not an add-on or something external, it is part and parcel of everything you do with computers (analogy with ES&H) Not “one-size-fits-all”, but appropriate for the needs and vulnerabilities of each system In most cases, it is simply common sense + a little information and care Each Division/Section or large experiment has a GCSC (General Computer Security Coordinator) who acts as liaison with the Computer Security Team in disseminating information and dealing with incident; see http://computing.fnal.gov/security/ for an up to date list
- 7. Strong Authentication Avoid disclosure of passwords on the network No network services (logon or read/write ftp) visible on the general internet can be offered with out requiring Kerberos authentication (unless a formal exemption is applied for and granted) Kerberos provides a single sign in, minimizing use of multiple passwords for different systems Lab systems are constantly scanned for violations of this policy
- 8. Critical Systems Defined as “critical to the mission of the Laboratory”, i.e. disruption may have major impact on Laboratory operations; Most things do not fall in this category; Special (more stringent) rules & procedures apply; Including periodic reviews; You’ll know if you’re in this category;
- 9. Critical Vulnerabilities and Vulnerability Scanning Certain security vulnerabilities are declared critical when they are (or are about to) being actively exploited and represent a clear and present danger Upon notification of a critical vulnerability, systems must be patched by a given date or they will be blocked from network access
- 10. Computer Security Incidents Mandatory incident reporting; Report all suspicious activity: If urgent to FCC Helpdesk, x2345, 24x7; Or to system manager (if immediately available); Non-urgent to computer_security@fnal.gov; Incidents investigated by Fermi Computer Incident Response Team (FCIRT); Not to be discussed!
- 11. FCIRT (Fermi Computer Security Incident Response Team) Security experts drawn from throughout the lab Investigate (“triage”) initial reports; Coordinate investigation overall; Work with local system managers; Call in technical experts; May take control of affected systems; Maintain confidentiality;
- 12. Other Rules for General Systems “ Blatant disregard” of computer security; First time warning, repeat offense disciplinary action; Unauthorized or malicious actions; Damage of data, unauthorized use of accounts, denial of service, etc., are forbidden; Ethical behavior; Same standards as for non-computer activities; Restricted central services; May only be provided by Computing Division; Security & cracker tools; Possession (& use) must be authorized;
- 13. Mandatory System Manager Registration System managers must be registered with FCSC See: http://www.miscomp.fnal.gov/sysadmindb
- 14. Your role as a user Guard against malicious code in email Don’t open attachments unless you are sure they are safe Don’t trust who email is from Updated and enabled virus signatures Guard against malicious code from web browsing
- 15. Your role - 2 Obey Strong Authentication Policy (Kerberos) Don’t run network services (login or read write ftp) unless they demand Kerberos authentication Treat your kerberos password as a sacred object (never expose it over the network) Promptly report potential computer security incidents X2345 or [email_address] Follow FCIRT instructions during incidents (especially about keeping infected machines off the network and preserving the status of an infected machine for expert investigation)
- 16. Other Computing Policy Issues Data backup Incidental use Privacy Offensive material Licensing
- 17. Data Backup Policy - Users Users (data owners) responsible for determining: What data requires protection; How destroyed data would be recovered, if needed; Coordinating backup plan w/ sysadmins; or doing their own backups; If the backup is done for you it might be worth occasionally checking that you can really retrieve the data
- 18. Incidental Computer Usage Fermilab permits some non business use of lab computers Guidelines are at http://computing.fnal.gov/security/ProperUse.htm
- 19. Activities to Avoid Large grey area, but certain activities are “over the line”; Illegal; Prohibited by Lab or DOE policy; Embarrassment to the Laboratory; Interfere w/ performance of job; Consume excessive resources;
- 20. Privacy of Email and Files Fermilab normally respects the privacy of electronic files and email; Employees and users are required to do likewise; Certain exemptions for system managers and computer security response; All others must have Director(ate) approval;
- 21. Privacy of Email and Files May not use information in another person’s files seen incidental to any activity (legitimate or not) for any purpose w/o either explicit permission of the owner or a “reasonable belief the file was meant to be accessed by others.” Whether or not group/world accessible; “Group” files implicitly may be used by the group for the mission of the group;
- 22. Offensive Material on computers Many “computer security” complaints are not; Material in a computer is like material in a desk; With respect to both privacy and appropriateness; This is a line management, not computer security, concern (except in egregious cases).
- 23. Software Licensing Fermilab is strongly committed to respecting intellectual property rights Any use of unlicensed commercial software is a direct violation of lab policy
- 24. Questions? [email_address] [email_address] for questions about security policy [email_address] for reporting security incident http://computing.fnal.gov/security