Identifying and Evaluating Controls

A control, also called a countermeasure, is a security control or a safeguard. A control is implemented to reduce a risk, and a risk can be reduced by reducing vulnerabilities or the impact of the threat.

When identifying and evaluating controls, the following should be considered:

  • In-place controls—In-place controls are those that are currently installed in the operational system.
  • Planned controls—Planned controls are those that have a specified implementation date.

In-Place and Planned Controls

Controls cost money. Before purchasing a control, an organization will evaluate its options. During its evaluation of alternative controls, the organization will gather relevant documentation. The documentation for these controls should be reviewed when performing a risk assessment because it can reveal several things.

If the control is in place, its effectiveness can be measured. Ideally, controls are as effective as they are expected to be, but some controls aren’t as effective as others. An intrusion detection system may have been added that produced a high level of false alarms, which caused administrators to eventually ignore them, or a spam appliance may have been added that marks valid emails as spam.

Why an in-place control is ineffective needs to be determined. The risk assessment can include an evaluation of this control to determine what to do differently. Knowing whether a control is effective is also important.

A planned control probably won’t be changed. However, reviewing the documentation that recommended it is still valuable. The current systems can be evaluated to ensure the original threats and vulnerabilities still exist. Additional tools or techniques may also exist that will allow the enhancement of the original recommendations.

Control Categories

Controls are organized or classified in several ways. One of the popular methods is to define them based on these three categories:

  • Procedural controls
  • Technical controls
  • Physical controls

The following sections explain these three categories, but other categories are also used. NIST has published many documents related to information security. SP 800-53 Rev. 4, Security and Privacy Controls for Federal Information Systems and Organizations, was released in April 2013.

NOTE

This section introduces the identification and evaluation of controls.

NIST SP 800-53 previous to revision 4 classified these families as Management Controls, Technical Controls, or Operational Controls. However, some controls within each family had combinations of management, technical, and operational classes. NIST removed these classifications in SP 800-53 Rev. 4. TABLE 6-1 shows the current NIST control families.

TABLE 6-1 NIST Control Families
CONTROL FAMILIES NUMBER OF CONTROLS
Access Control 23
Awareness and Training 4
Audit and Accountability 16
Security Assessment and Authorization 8
Configuration Management 11
Contingency Planning 12
Identification and Authentication 11
Incident Response 10
Maintenance 6
Media Protection 8
Physical and Environmental Protection 19
Planning 6
Personnel Security 8
Risk Assessment 5
System and Services Acquisition 20
System and Communications Protection 41
System and Information Integrity 16
Program Management 16

No matter how the controls are listed, the goals are the same, to protect the confidentiality, integrity, and availability of systems and data.

Procedural Controls

Procedural controls are the controls placed in response to the rules and guidelines directed by upper-level management, and they include several specific controls. However, one important point about procedural controls is that they are implemented with a written document.

Examples of procedural controls are:

  • Policies and procedures—This control may be an organization’s security policy. For example, it could also be the specific procedures used to back up a server.
  • Security plans—These plans are comprehensive to help an organization deal with different events. For example, a disaster recovery plan helps an organization plan for a disaster, such as a hurricane or an earthquake.
  • Insurance—Insurance can reduce the impact of a risk. Common examples include fire insurance and flood insurance.
  • Personnel checks—An organization may have policies in place to perform different types of checks on personnel; they could include background checks or financial checks.
  • Awareness and training—Many organizations regularly take steps to raise the security awareness of personnel, which can be done through, for example, formal training, posters, and emails.
  • Rules of behavior—Many organizations use rules of behavior, also called acceptable use policies (AUPs), to let people know what they can do with computers and systems. An AUP is often a document that users read and sign when they are hired. Commonly, employees are required to review the documents on a regular basis, such as once a year.

NOTE

Previous versions of NIST SP 800-53 referred to procedural controls as administrative controls.

Technical Controls

A technical control uses computers or software to protect systems. The benefit of a technical control is that it is automated, which means that it is set once and will consistently enforce the control.

Some examples of technical controls are:

  • Logon identifier—Users are required to provide credentials before they are granted access to the system, which is also referred to as authentication. Three primary factors of authentication exist:
    • Something the user knows, such as a username and password
    • Something the user has, such as a smart card
    • Something about the user, such as information captured by biometrics
  • Session time-out—Many systems automatically time out after a period of inactivity. For example, a password-protected screen saver locks a computer after a specific number of minutes. When the time has passed, the screen saver starts, and the user must enter credentials before accessing the system again.
  • System logs—System logs record activity performed by systems, users, or attackers. For example, a system log can identify when a server was shut down or when specific services were stopped or started. Application logs can record specific application activity.
  • Audit trails—Many types of audit logs can be used to create an audit trail. A security log can record all access to specific files, and a firewall log can record all traffic entering or leaving a network.
  • Input validation—Applications can use data range and reasonableness checks to validate data before using it. As a simple example, dividing by zero is impossible. A program that accepts values used in a divide operation can ensure the value is not zero before using it.
  • Firewalls—Network firewalls can control traffic coming into and out of a network. Host-based firewalls can restrict traffic for individual systems.
  • Encryption—Data can be encrypted when it is stored on a drive or transmitted over a network, which provides confidentiality of the data.
Physical Controls

A physical control controls the physical environment. Physical controls include locks and guards to restrict physical access and elements to control the environment, such as heating and cooling systems.

Examples of physical controls are:

  • Locked doors—Server rooms can be locked to protect servers, and wiring closets that host routers and switches can be locked. Proprietary data can also be protected, such as employee files or research data, by locking doors and filing cabinets.
  • Guards and access logs—Guards can be hired to control access to sensitive areas, such as at the front entrance of a building or in internal areas, and an access log can be used to list individuals who have authorized access. The guard then allows access only to personnel on this list. Access logs can also be used to record individuals who have accessed a room.
  • Video cameras—Cameras can monitor areas on a continuous basis. Closed circuit television (CCTV) systems work very well as a deterrent because many CCTV systems can record data from multiple cameras.
  • Fire detection and suppression—A fire can destroy a significant amount of data and hardware in a very short period of time. Effective detection and suppression systems detect the fire before it gets too big and then quickly extinguish it.
  • Water detection—Some areas are prone to flooding. When water is detected, pumps can be turned on automatically to remove the water. If the flooding can’t be controlled, the detection system can turn off electrical systems to reduce possible damage.
  • Temperature and humidity detection—Systems need to operate within certain temperature ranges. If they get too hot, electrical components overheat and fail. High humidity can cause condensation on the systems, which can also cause failures. Heating, ventilation, and air-conditioning (HVAC) systems control the temperature and humidity.
  • Electrical grounding and circuit breakers—Proper grounding ensures that dangerous voltage is routed to ground when electrical systems fail. Grounding protects equipment and personnel, and circuit breakers protect systems and wiring. When a failure results in excess current, the circuit breaker will cut the power before the excess current can start a fire or damage the equipment.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.227.46.229