Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
Top
Top

Table of Contents

Anchor
Getting Started
Getting Started

Tip
titleGetting Started

Operations security involves planning and sustaining the day-to-day “rubber meets the road” processes that are critical to maintaining the security of institutions’ information environments. The extent and complexity of security operations will vary between institutions based on institutional risk tolerances and resource levels. However, each of the control areas in this chapter must be addressed in some manner to help mitigate common ubiquitous risks. The most important aspect of operations security is that the operations themselves need to be repeatable, reliable, and consistently performed.

If you are just starting an information security program or looking to evaluate and improve operations security then the following approach can be very helpful:

  1. Review the following areas to assess the confidentiality, integrity, and availability of operations center controls:
    1. Operational procedures and responsibilities
      1. Review documentation and evaluate guidance in regards to change management, capacity management, and separation of development, test, and production environments
    2. Malware detection and prevention controls
      1. Evaluate their level of effectiveness
    3. Data center backup strategy
      1. Evaluate whether backup procedures and methods (e.g., encryption) are effective both for on- and off-premises backup management
    4. Audit trails and logging
      1. Review whether they are implemented effectively so that security reviews can be conducted to detect tampering, unauthorized access, and record user activities
    5. Installation of software on operational systems
      1. Ensure licensing requirements are met
  2. Implement a formal vulnerability management program to proactively test IT infrastructure for vulnerabilities that can be exploited and ensure that there is an effective process in place to manage corrective actions in collaboration with stakeholders.

  3. Prepare in advance for IT controls audits to avoid service disruptions.

Operations SecurityTop of page

Anchor
Overview
Overview

Overview

To be effective in reducing information security risk and ensuring correct computing, the security program needs to include operational procedures, controls, and well-defined responsibilities. These are complemented and often necessitated by formal policies, procedures, and controls which are necessary to protect exchange of data and information through any type of communication media or technology.

...

  • Operational Procedures and Responsibilities (important operational processes include: Change Management; Capacity Management; Separation of Development, Test, and Operations Environments)
  • Protection from Malware
  • Backups
  • Logging and Monitoring
  • Control of Operational Software
  • Technical Vulnerability Management
  • Information System Audit Considerations

Operations Security Top of page

Anchor
Procedures
Procedures

Operational Procedures and Responsibilities (ISO 12.1)

Panel
bgColor#FFFFCE

Objective: To ensure the effective operation and security of information processing facilities.

Documented Operating Procedures

Key Question: Do we have a procedures that are readily available, periodically updated, and consistently executed? 

...

Change Management Procedures

Key Question: Do we have a formal method for classifying, evaluating, and approving changes?

...

Capacity Management Procedures

Key Question: Do we monitor resource utilization and establish projections of capacity requirements to ensure that we maintain service performance levels?

...

Operations Security Top of page

Anchor
Malware
Malware

Protection from Malware (ISO 12.2)

Panel
bgColor#FFFFCE

Objective: To protect the confidentiality, integrity, and availability (CIA) of information technology resources and data.

...

Operations Security Top of page

Anchor
Backups
Backups

Backups (ISO 12.3)

Panel
bgColor#FFFFCE

Objective: To ensure the integrity and availability of information processed and stored within information processing facilities.

...

Operations Security Top of page

Anchor
Monitoring
Monitoring

Logging and Monitoring (ISO 12.4)

Panel
bgColor#FFFFCE

Objective: To detect unauthorized activities occurring that may have a detrimental effect upon information processing facilities.

...

Operations Security Top of page

Anchor
Control
Control

Control of Operational Software (ISO 12.5)

Panel
bgColor#FFFFCE

Objective: To ensure the integrity of operating systems.

...

Operations Security Top of page

Anchor
Vulnerability
Vulnerability

Technical Vulnerability Management (ISO 12.6)

Panel
bgColor#FFFFCE

Objective: To prevent exploitation of technical vulnerabilities.

...

(lightbulb) Campus Case Study: Enhancing Application Security with a Web Application Firewall - UC, Irvine

Technical Vulnerability Scanning

Depending on the size and structure of the institution, the approach to vulnerability scanning might differ. Small institutions that have a good understanding of IT resources throughout the enterprise might centralize vulnerability scanning. Larger institutions are more likely to have some degree of decentralization, so vulnerability scanning might be the responsibility of individual units. Some institutions might have a blend of both centralized and decentralized vulnerability assessment. Regardless, before starting a vulnerability scanning program, it is important to have authority to conduct the scans and to understand the targets that will be scanned.

Vulnerability scanning tools and methods are often somewhat tailored to varied types of information resources and vulnerability classes. The table below shows several important vulnerability classes and some relevant tools.

 

Common Types of Technical VulnerabilitiesRelevant Assessment Tools
Application Vulnerabilities

Web Application Scanners (static and dynamic), Web Application Firewalls

Network Layer Vulnerabilities

Network Vulnerability Scanners, Port Scanners, Traffic Profilers 

Host/System Layer VulnerabilitiesAuthenticated Vulnerability Scans, Asset and Patch Management Tools, Host Assessment and Scoring Tools

Common Challenges

  • "Scanning Can Cause Disruptions." IT operations teams are quite reasonably very sensitive about how vulnerability scans are conducted and keen to understand any potential for operational disruptions. Often legacy systems and older equipment can have issues even with simple network port scans; To help with this issue, it can often be useful to build confidence in scanning process by partnering with these teams to conduct risk evaluations before initiating or expanding a scanning program. It is also often important to discuss the “scan windows” when these vulnerability assessments will occur to ensure that they do not conflict with regular maintenance schedules.

  • "Drowning In Vulnerability Data and False Positives." Technical vulnerability management practices can produce very large data-sets. It is important to realize that just because a tool indicates that a vulnerability is present that there are frequently follow-up evaluations needed validate these findings. Reviewing all of these vulnerabilities is usually infeasible for many teams; For this reason, it is very important to develop a vulnerability prioritization plan before initiating a large number of scans. These priority plans should be risk driven to ensure that teams are spending their time dealing with the most important vulnerabilities in terms of both likelihood of exploitation and impact.

Operations SecurityTop of page

Anchor
Audit
Audit

Information Systems Audit Considerations (ISO 12.7)

Panel
bgColor#FFFFCE

Objective: Minimize the impact of audit activities on operational systems.

...

Any and all audit activity, to assess an operational system, should always be managed to minimize any impact on the system during required hours of operation. Any testing of operational systems that could pose an adverse effect to the system should be conducted during off hours.

Operations Security Top of page

Anchor
Resources
Resources

Resources

Panel
bgColor#ADD8E6

Campus Case Studies On This Page
(lightbulb) Enhancing Application Security with a Web Application Firewall - UC, Irvine (2011)

EDUCAUSE Resources
EDUCAUSE Resources & Resource Center Pages

HEISC Toolkits/Guidelines

Templates/Sample Plans

Security Professionals Conference 2014

Security Professionals Conference 2013

Enterprise IT Leadership Conference 2013

EDUCAUSE Annual Conference 2012

Security Professionals Conference 2012

Southeast Regional Conference 2012

Mid-Atlantic Regional Conference 2012

EDUCAUSE Annual Conference 2011

Security Professionals Conference 2011

Initiatives, Collaborations, & Other Resources

  • ECAR Working Groups; Bring together higher education IT leaders to address core technology challenges.

Operations Security Top of page

Anchor
Standards
Standards

Standards

ISO

NIST

COBIT

PCI DSS

2014 Cybersecurity Framework

HIPAA Security

27002:2013 Information Security Management
Chapter 12: Operations Security
ISO/IEC 27003:2010
ISO/IEC 27004:2009

800-100: Information Security Handbook: A Guide for Managers
800-53: Recommended Security Controls for Federal Information
Systems and Organizations
800-14: Generally Accepted Principles and Practices for Securing
Information Technology Systems

APO12.01
APO12.02
APO12.03
APO12.04
APO13.01
BAI01.06
BAI06.01
BAI07.04
BAI10.01
BAI10.02
BAI10.03
BAI10.05
DSS02.07
DSS05.01 

Req 2
Req 6
Req 12

ID.BE-4
ID.4A-1
ID.RA-5
PR.DS-4
PR.DS-6
PR.DS-7
PR.IP-1
PR.IP-3
PR.IP-4
PR.IP-12
PR.PT-1
DE.CM-3
DE.CM-4
DE.CM-5
DE.CM-8

45 CFR 164.308(a)(5)(ii)(B)
45 CFR 164.308(a)(7)(ii)(A)
45 CFR 164.308(a)(7)(ii)(A)
45 CFR 164.316(a), 45 CFR 164.316(b)(1)
45 CFR 164.308(a)
45 CFR 164.310(d)(1)
45 CFR 164.310(d)(2)(iv)
45 CFR 164.312(c)(1)
45 CFR 164.312(b)
45 CFR 164.308(a)(5)
45 CFR 164.312(a)(1)

Operations SecurityTop of page

...

(question) Questions or comments? (info) Contact us.

...