EVOPEDIA

← all systems · see it in The System

Information security

Information security (infosec) is the practice of protecting information by mitigating information risks; it is part of information risk management (src:wp:information-security). NIST defines it as 'the protection of information and systems from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide confidentiality, integrity, and availability' (src:nist-sp800-12r1). Protected information may take any form: electronic or physical, tangible (paperwork) or intangible (knowledge). Walked here as the practice (its goals, people, standards, laws, models and history) together with what it protects; the computer-side reading of the same practice is sys:computer-security (walked wave 13), whose floors this walk points at instead of repeating.

Properties published scienceour proposal

Sourced fields, and our own readings.

born atcontested (C-1357): 'since the early days of communication'; or WWII and the computer era
born precisionnone; no dated first case in the sources read
boundaryInside: the goals (confidentiality, integrity, availability, and the attributes and definitions argued over them), the work of protecting information (identifying and classifying assets, assessing risk, choosing and running controls of physical, technical and administrative kinds, monitoring, incident handling, business continuity, change management), the people who do it (owners, risk executives, CISOs, auditors, security staff, every employee who handles information) and the bodies of standards, models and law that shape it. Outside, protected by it: the information itself in any form (paper, electronic, knowledge, genomes) and the organisations, states and people whose mission it serves; the adversaries and accidents it guards against (walked from the attacker's side in computer-security's secondary stack); the tools it borrows (cryptography, operating systems, networks). The edge with computer security and cyber security is contested (C-1156): 'cyber security goes beyond the boundaries of traditional information security' (src:von-solms-2013), while the encyclopedia files computer security as its subdiscipline.
nested levelA practice carried by people and organisations (rung 11), since the 1960s largely run on computers and networks (rung 12); part of information risk management; serves organisations' missions; shaped by law, markets and states. Built from controls, roles, standards and its subdiscipline computer security; borrows cryptography as a tool.
scalesocial

Measures (14) published science

characteristic clock: crowd-sourced phishing reportsabout 10% within 5 min; 20% within 15 min; 30-40% within 30 min share of all reports of a simulated phish, by time after delivery
employees who clicked at least one simulated phish (15 months)4,729 of 14,733 (32.10%) employees
simulated phishing emails clicked5.67 % of 117,864 sent
reports by employees in 15 months14,401 (11,035 of them simulated) emails reported
Gordon-Loeb bound on optimal security investment< 1/e (about 37%) of the expected loss
Willemson counterexample to the GL boundup to 50%; close to 100% when assumptions relax of the expected loss
FIPS 199 impact levels3 (LOW, MODERATE, HIGH) plus NOT APPLICABLE for confidentiality levels per security objective
security objectives in US federal law3 objectives (confidentiality, integrity, availability)
attributes in the Parkerian Hexad6 attributes
NIST control families20 information security and privacy control families (SP 800-53, as introduced in SP 800-12r1)
CISSP holders worldwide191,036 ISC2 members holding the CISSP (December 2025)
information-security behaviour studies in health information systems35 studies; 20 distinct theories studies (systematic review)
dimensions of information security culture7 dimensions (Roer and Petric 2017)
Anderson 1972 planning study duration2 February to 1 September 1972 study period

Open contentions (6) open contention

Where sources or readings disagree. Both stay on the map.

Cross-scale patterns seen here (21) our proposal

Shapes that recur when the same kind of problem is solved at different scales, and how each shows in Information security. Each links to every other system that shows it.

Valence: what it trades, and with whom (34) published science

Each exchange with a neighbour, read from both sides: who gains, who pays, and what carries it.

Partners and parts published science

Built from / builds (15)

Sits inside / holds (19)

expressed by (26)

floor filled by (29)

represents (1)

same practice as (1)

Kinds (4)

wired (1)

Notes published science

Layers

The ways it takes in its world, where they meet, and how it acts back, each from L1 (where it meets the world) up.

information security as practitioners describe it: information in any form up to the mission it serves (reader's view)

  1. L1: Information in any form (paperwork, electronic data, knowledge, genomes) and the world threats come from: people with intent, accidents, nature, failing infrastructure
  2. L2: Assets known: identified, valued, owned and classified (labels from Public to Top Secret, TLP colours)
  3. L3: Controls: physical (fences, guards, safes), technical (access control, encryption, the reference monitor) and administrative (policies, procedures, training); identification, authentication and authorization
  4. L4: Monitoring and incident handling: audit trails, continuous monitoring, user reports, incident response plans and teams
  5. L5: Risk management: categorise information by impact, assess threats and vulnerabilities, treat risk (accept, mitigate, transfer, deny), carry residual risk; business continuity
  6. L6: Policy, standards, law and culture; roles and responsibilities made explicit (risk executive, CIO, CISO, owners, users); formal models
  7. L7: Purpose: confidentiality, integrity and availability (or appropriate access for each stakeholder) in service of the organisation's mission

the boardroom (shared floors)

  1. L4: Monitoring and incident handling: continuous monitoring, audit review, report triage, incident response plans and teams (computer-security's b-detect and b-respond are this floor for computers)
  2. L5: Risk management: categorise, assess, choose controls, accept residual risk, plan continuity
  3. L6: Policy, standards, law, culture and explicit roles (risk executive, CIO, senior information security officer or CISO, owners, users); formal models adopted
  4. L7: Purpose and governance: the security goals (CIA, or appropriate access) in service of the mission, owned by senior management

the paper era: marked documents, trusted carriers and clearances (secondary stack)

  1. L1: Correspondence and documents carried between diplomats, commanders and offices
  2. L2: Markings on the document, trusted carriers, guarded strong boxes
  3. L3: Multi-tier classification and markings saying who may handle a document and where it is stored
  4. L4: Clearances, need-to-know and operating procedures (Ware's two organisational leakage points), proper destruction
  5. L5: Secrecy law and official classification systems (Official Secrets Act 1889; the Bell-LaPadula levels for computers)

way in: Audit trails and monitoring records

  1. L1: Every authentication and access attempt
  2. L2: An audit trail for every access
  3. L3: Continuous monitoring keeps awareness current

way in: Incidents, breaches and losses

  1. L1: A threat uses a vulnerability: harm, an impact
  2. L2: The impact read as a loss of confidentiality, integrity or availability
  3. L3: Counted and reported (ransomware in health care: disrupted care, integrity at risk; reporting limited)
  4. L4: The expected loss that investment is weighed against

way in: Information assets (what there is to protect)

  1. L1: Information in any form: paper, electronic, knowledge
  2. L2: Assets identified and valued: people, buildings, hardware, software, data, supplies
  3. L3: An owner named and a classification policy written
  4. L4: Each information type categorised by the impact of losing C, I or A

way in: Laws and regulation

  1. L1: Laws and regulations on how data is accessed, processed, stored, transferred and destroyed
  2. L2: Specific acts (Computer Security Act 1987, FISMA 2002 and 2014, HIPAA, GLBA, breach notification laws)
  3. L3: Liability: who carries it sets the care taken
  4. L4: Security objectives defined in law
  5. L5: Compliance requirements (breach notification, auditor attestation)

way in: People's attitudes, behaviour and culture

  1. L1: People perceive and decide about risk in different ways
  2. L2: What employees think and feel, and what they do
  3. L3: Individual and organisational factors measured
  4. L4: Seven dimensions of security culture (attitudes, behaviours, cognition, communication, compliance, norms, responsibilities)
  5. L5: Culture evaluated and changed in cycles

way in: People's reports of suspicious messages and events

  1. L1: Phishing and other suspicious emails reach employees in their working context
  2. L2: The employee judges it; type of computer use predicts vulnerability better than amount
  3. L3: A report button in the email client

way in: Physical and environmental events

  1. L1: Power failures, communications loss, water leaks, fire, flood, storms, strikes
  2. L2: System downtime, sometimes with the systems still working (staff can't reach them)
  3. L3: Physical protection, continuous in time

way in: Standards and frameworks

  1. L1: Published guidance against threats to a user's or organisation's cyber environment
  2. L2: Families of standards: ISO/IEC 27000 (ISMS), Common Criteria, NIST CSF, FIPS and SPs
  3. L3: Control catalogues: 20 control families
  4. L4: Certification of practitioners (CISSP)
  5. L5: Assessment criteria and certification of organisations

way in: The field's own models and research

  1. L1: Principles learned from experience, for want of a complete method
  2. L2: Formal models: the reference monitor; Bell-LaPadula's basic security theorem
  3. L3: Economic models: perverse incentives, the Gordon-Loeb investment model
  4. L4: Definitions argued (CIA, the hexad, appropriate access)

way in: The mission and its stakeholders' needs

  1. L1: The organisation's mission
  2. L2: The system's role in it
  3. L3: Who should have what access, relative to each stakeholder
  4. L4: Security requirements stated in mission terms

way in: Threat sources (adversarial and non-adversarial)

  1. L1: Acts of nature, war, accidents and malicious acts from inside or outside; passive interception of emanations
  2. L2: Threat sources named: malicious hackers and their subcategories, insiders, fraud, malicious code, errors, infrastructure loss
  3. L3: A threat assessment
  4. L4: The likelihood that a threat will use a vulnerability

way in: Vulnerabilities (weaknesses)

  1. L1: Weaknesses in people, process and technology
  2. L2: Errors, omissions and bugs, unnoticed in normal use
  3. L3: A vulnerability assessment, with the probability of exploitation
  4. L4: Controls themselves evaluated for vulnerabilities

way out: Awareness and training

  1. L1: Every employee and partner trained on the classification scheme (simulated phishing with embedded training: contested)
  2. L6: Regular security awareness training

way out: Breach notification and reporting

  1. L1: Reports filed (often late; reporting gives a limited view)
  2. L6: Notification required by law

way out: Changes made under change management

  1. L1: The change implemented at the appointed time
  2. L4: Each change tested before production, with a back-out plan
  3. L6: A change review board oversees changes

way out: Continuity and recovery

  1. L1: Critical ICT infrastructure recovered after a disaster
  2. L3: Backups scheduled, critical elements duplicated
  3. L5: Business continuity management

way out: Controls chosen and applied

  1. L1: On the medium: locks and safes, encryption of information in transit and in storage
  2. L3: Physical, technical and administrative controls in overlapping layers
  3. L5: Controls selected from the risk assessment

way out: Incident response: contain, revoke, recover

  1. L1: Access revoked: a terminated employee's access disabled and the person escorted off the premises
  2. L4: An incident response plan is activated

way out: Labels and handling rules written onto information

  1. L1: Marks on the information itself
  2. L2: Labels by sector: business, government, Traffic Light Protocol
  3. L6: A classification policy

way out: Risk transferred (insurance, outsourcing)

  1. L1: Cyber-insurance bought beside security investment
  2. L5: Leadership chooses to transfer a risk

Who fills each layer

Sources (48) published science

Computer security (Wikipedia)
Information security (Wikipedia, via Wikimedia Enterprise snapshot)
Lain D, Kostiainen K, Capkun S (2022) Phishing in organizations: findings from a large-scale and long-term study. IEEE S&P 2022; arXiv:2112.07498 (behind its links)
von Solms R, van Niekerk J (2013) From information security to cyber security. Computers & Security 38:97-102. doi:10.1016/j.cose.2013.04.004 (behind its links)
Lundgren B, Moller N (2019) Defining information security. Sci Eng Ethics 25:419-441. doi:10.1007/s11948-017-9992-1 (PMC6450831) (behind its links)
Skeoch HRK (2022) Expanding the Gordon-Loeb model to cyber-insurance. Computers & Security (author preprint, UCL Discovery 10138028) (behind its links)
NIST (2004) FIPS PUB 199: Standards for Security Categorization of Federal Information and Information Systems. doi:10.6028/NIST.FIPS.199 (behind its links)
Parkerian Hexad (Wikipedia, via Wikimedia Enterprise) (behind its links)
Nieles M, Dempsey K, Pillitteri VY (2017) NIST SP 800-12 Rev. 1: An Introduction to Information Security. doi:10.6028/NIST.SP.800-12r1 (behind its links)
Certified Information Systems Security Professional (Wikipedia, via Wikimedia Enterprise snapshot) (behind its links)
Sari PK et al. (2022) Information security behavior in health information systems: a review of research trends and antecedent factors. Healthcare 10:2531. doi:10.3390/healthcare10122531 (PMC9777837) (behind its links)
Anderson JP (1972) Computer Security Technology Planning Study, Vol. I (ESD-TR-73-51) (behind its links)
Bell DE, LaPadula LJ (1976) Secure Computer System: Unified Exposition and Multics Interpretation (MTR-2997 Rev. 1, ESD-TR-75-306) (behind its links)
Authentication (Wikipedia, via Wikimedia Enterprise snapshot) (behind its links)
Access control (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Scarfone, K. & Mell, P. (2007). Guide to Intrusion Detection and Prevention Systems (IDPS). NIST Special Publication 800-94. doi:10.6028/NIST.SP.800-94 (behind its links)
Vielberth, M., Böhm, F., Fichtinger, I. & Pernul, G. (2020). Security Operations Center: A Systematic Study and Open Challenges. IEEE Access 8:227756-227779. doi:10.1109/ACCESS.2020.3045514 (CC BY 4.0; University of Regensburg repository copy) (behind its links)
Computer security incident management (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Homoliak et al. 2019, Insight into Insiders and IT: A Survey of Insider Threat Taxonomies, Analysis, Modeling, and Countermeasures, ACM Computing Surveys (arXiv:1805.01612) (behind its links)
Scarfone K, Hoffman P. Guidelines on Firewalls and Firewall Policy. NIST Special Publication 800-41 Revision 1, 2009 (doi:10.6028/NIST.SP.800-41r1) (behind its links)
Anderson R. Security Engineering, 2nd ed., chapter 11: Physical Protection (Wiley 2008; author's free copy) (behind its links)
Privacy (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Supply chain attack (Wikipedia, via Wikimedia Enterprise snapshot) (behind its links)
Social engineering (security) (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Scarfone K, Souppaya M, Cody A, Orebaugh A (2008). NIST SP 800-115: Technical Guide to Information Security Testing and Assessment. NIST (behind its links)
Wilson M, Hash J. NIST SP 800-50: Building an Information Technology Security Awareness and Training Program (October 2003) (behind its links)
Information security audit (encyclopedia) (behind its links)
Defense in depth (computing) (Wikipedia, via Wikimedia Enterprise) (behind its links)
Erlich Y, Narayanan A (2014) Routes for breaching and protecting genetic privacy. Nat Rev Genet 15:409-421; bioRxiv 10.1101/000042 (CC BY) (behind its links)
Ware WH (ed.) (1970) Security Controls for Computer Systems: Report of Defense Science Board Task Force on Computer Security (RAND R-609-1; NIST early papers copy) (behind its links)
Neprash, McGlave, Cross, Virnig, Puskarich, Huling, Rozenshtein and Nikpay, Trends in Ransomware Attacks on US Hospitals, Clinics, and Other Health Care Delivery Organizations, 2016-2021, JAMA Health Forum 3(12), 2022 (doi:10.1001/jamahealthforum.2022.4873; PMC9856685) (behind its links)
Electrical grid (Wikipedia, via the Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Wikipedia: Operating system (behind its links)
Szekeres L, Payer M, Wei T, Song D 2013. SoK: Eternal war in memory. IEEE Symposium on Security and Privacy (author copy) (behind its links)
Malware (Wikipedia, via Wikimedia Enterprise snapshot) (behind its links)
Cichonski P, Millar T, Grance T, Scarfone K (2012) Computer Security Incident Handling Guide. NIST Special Publication 800-61 Rev. 2. doi:10.6028/NIST.SP.800-61r2 (US government work, not subject to copyright) (behind its links)
Threat actor (Wikipedia, via Wikimedia Enterprise snapshot) (behind its links)
Joint Task Force Transformation Initiative (2011). NIST SP 800-39, Managing Information Security Risk: Organization, Mission, and Information System View. doi:10.6028/NIST.SP.800-39 (behind its links)
Organization (Wikipedia, via Wikimedia Enterprise snapshot) (behind its links)
Database (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Cloud computing (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01; page flagged 'AI-generated' additions 2025-26) (behind its links)
Vulnerability (computer security) (Wikipedia, via Wikimedia Enterprise snapshot) (behind its links)
Souppaya M, Scarfone K, Dodson D. Secure Software Development Framework (SSDF) version 1.1. NIST SP 800-218, 2022, doi:10.6028/NIST.SP.800-218 (behind its links)
Moore T, Clayton R, Anderson R (2009) The Economics of Online Crime. Journal of Economic Perspectives 23(3):3-20, doi:10.1257/jep.23.3.3 (behind its links)
IT disaster recovery (Wikipedia) (behind its links)
Saltzer and Schroeder, The Protection of Information in Computer Systems, Proceedings of the IEEE 63(9), 1975 (doi:10.1109/PROC.1975.9939) (behind its links)
Anderson, Why Information Security is Hard: An Economic Perspective, ACSAC 2001 (doi:10.1109/ACSAC.2001.991552) (behind its links)
Herley, So Long, And No Thanks for the Externalities: The Rational Rejection of Security Advice by Users, NSPW 2009 (doi:10.1145/1719030.1719050) (behind its links)