1computer security
In the early days of computers, this term specified the need to secure the physical location of computer technology from outside threats. This term later came to represent all actions taken to preserve computer systems from losses. It has evolved into the current concept of information security as the scope of protecting information in an organization has expanded.
2Security
A state of being secure and free from danger or harm. Also, the actions taken to make someone or something secure.
3information security
Protection of the confidentiality, integrity, and availability of information assets, whether in storage, processing, or transmission, via the application of policy, education, training and awareness, and technology.
4network security
A subset of communications security ; the protection of voice and data networking components, connections, and content.
5C.I.A. triad
The industry standard for computer security since the development of the mainframe. The standard is based on three characteristics that describe the utility of information: confidentiality, integrity, and availability.
6Access
A subject or object’s ability to use, manipulate, modify, or affect another subject or object. Authorized users have legal access to a system, whereas hackers must gain illegal access to a system.
7Asset
The organizational resource that is being protected.
8Attack
An intentional or unintentional act that can damage or otherwise compromise information and the systems that support it.
9Control, safeguard, or countermeasure
Security mechanisms, policies, or procedures that can successfully counter attacks, reduce risk, resolve vulnerabilities, and otherwise improve security within an organization.
10Exploit
A technique used to compromise a system.
11Exposure
A condition or state of being exposed, exists when a vulnerability is known to an attacker
12Loss
A single instance of an information asset suffering damage or destruction, unintended or unauthorized modification or disclosure, or denial of use
13Protection profile or security posture
The entire set of controls and safeguards, including policy, education, training and awareness, and technology, that the organization implements to protect the asset
14Risk
The probability of an unwanted occurrence, such as an adverse event or loss
15Subjects and objects of attack
A computer can be either the subject of an attack—an agent entity used to conduct the attack—or the object of an attack: the target entity
16Threat
Any event or circumstance that has the potential to adversely affect operations and assets.
17Threat agent
The specific instance or a component of a threat.
18Threat event
An occurrence of an event caused by a threat agent.
19Threat source
A category of objects, people, or other entities that represents the origin of danger to an asset
20Availability
An attribute of information that describes how data is accessible and correctly formatted for use without interference or obstruction.
21Accuracy
An attribute of information that describes how data is free of errors and has the value that the user expects.
22Authenticity
An attribute of information that describes how data is genuine or original rather than reproduced or fabricated.
23confidentiality
An attribute of information that describes how data is protected from disclosure or exposure to unauthorized individuals or systems.
24personally identifiable information (PII)
Information about a person’s history, background, and attributes that can be used to commit identity theft. This information typically includes a person’s name, address, Social Security number, family information, employment history, and financial information.
25integrity
An attribute of information that describes how data is whole, complete, and uncorrupted.
26utility
An attribute of information that describes how data has value or usefulness for an end purpose.
27possession
An attribute of information that describes how the data’s ownership or control is legitimate or authorized.
28McCumber Cube
A graphical representation of the architectural approach widely used in computer and information security; commonly shown as a cube composed of 3×3×3 cells, similar to a Rubik’s Cube.
29Physical security
The protection of physical items, objects, or areas from unauthorized access and misuse.
30bottom-up approach
A method of establishing security policies and/or practices that begins as a grassroots effort in which systems administrators attempt to improve the security of their systems.
31top-down approach
A methodology of establishing security policies and/or practices that is initiated by upper management.
32systems development life cycle (SDLC)
A methodology for the design and implementation of an information system. The SDLC contains different phases depending on the methodology deployed, but generally the phases address the investigation, analysis, design, implementation, and maintenance of an information system.
33methodology
A formal approach to solving a problem based on a structured sequence of procedures.
34waterfall model
A type of SDLC in which each phase of the process “flows from” the information gained in the previous phase, with multiple opportunities to return to previous phases and make adjustments.
35software assurance
A methodological approach to the development of software that seeks to build security into the development life cycle rather than address it at later stages. SA attempts to intentionally create software free of vulnerabilities and provide effective, efficient software that users can deploy with confidence.
36chief information officer
An executive-level position that oversees the organization’s computing technology and strives to create efficiency in the processing and access of the organization’s information.
37chief information security officer (CISO)
Typically considered the top information security officer in an organization. The CISO is usually not an executive-level position, and frequently the person in this role reports to the CIO.
38project team
A small functional team of people who are experienced in one or multiple facets of the required technical and nontechnical areas for the project to which they are assigned.
39data owners
Individuals who control, and are therefore responsible for, the security and use of a particular set of information, may rely on custodians for the practical aspects of protecting their information, specifying which users are authorized to access it, but they are ultimately responsible for it.
40data custodians
Individuals who work directly with data owners and are responsible for storage, maintenance, and protection of information.
41data users
Internal and external stakeholders (customers, suppliers, and employees) who interact with information in support of their organization’s planning and operations.
42communities of interest
A group of individuals who are united by similar interests or values within an organization and who share a common goal of helping the organization to meet its objectives.