{ "model": { "rank": 3133, "code": "thing-q3510521", "model_id": "vr.tr.computer-security", "name": "computer security", "purpose": "Let an agent explain computer security concepts and practices, help people and organisations protect systems and respond to incidents, explain standards and law, and decline requests to attack or compromise systems without authorisation.", "family": "Thing Registry", "category": "Cross-cutting context", "status": "research-draft", "kind": "thing", "plane": "XCT", "domain": "XCT.STA", "industry": "", "version": "", "url": "/models/thing/q3510521/", "tier": 2, "score": 90, "payload": { "layer": "wikidata", "aliases": [ "cyber intelligence", "cyber resilience", "internet safety", "hardware security", "internet security", "capability-based security", "Group-IB Threat Intelligence", "Group-IB Fraud Protection", "Group-IB Managed eXtended Detection and Response", "Group-IB Attack Surface Management", "Group-IB Digital Risk Protection", "Group-IB Business Email Protection", "Group-IB Incident Response", "Group-IB Digital Forensics", "Group-IB Cyber Investigations", "Psychology in cybersecurity", "cyber threat hunting", "key expiration", "mobile security", "Unix security", "computer security model", "security operations center", "provable security", "network security", "browser security", "Capability-based addressing", "DHCP snooping" ], "aliasCount": 27, "merged": 27, "knownIn": 90, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q3510521", "url": "https://www.wikidata.org/wiki/Q3510521", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-11T19:59:16Z", "providers": [ "Claude" ], "breadth": "written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify", "pass": 2, "wave": 2, "engine": "claude" }, "metaModel": { "id": "THING-Q3510521", "registryId": "vr.tr.computer-security", "name": "computer security", "version": "0.2.0-wave.2", "entryKind": "thing", "family": "Thing Registry", "domain": [ "XCT.STA" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q3510521/", "model": { "registry_id": "vr.tr.computer-security", "name": "computer security", "purpose": "Let an agent explain computer security concepts and practices, help people and organisations protect systems and respond to incidents, explain standards and law, and decline requests to attack or compromise systems without authorisation.", "definition": "The protection of computer systems, networks, software and data from unauthorised access, damage, disruption and theft, through practices such as access control, encryption, patching, monitoring, secure design and user education, and disciplines including hardware security, internet safety and cyber resilience; it is governed by standards and law and practised defensively by organisations and individuals.", "what_it_is_for": "Protecting systems and data.", "affordances": [ "explain threats and defences", "give practical security guidance", "support incident response and reporting", "explain standards and legal obligations" ], "distinguishing_features": [ "Protects confidentiality, integrity and availability", "Technical and human measures", "Standards-based", "Legally regulated" ], "appearance": "Not physical; practices, controls and policies.", "visual_identification": [ "Defensive measures and controls", "Standards and audits", "Attacking systems without authorisation is a crime, not security" ], "physical_properties": [], "families_and_kinds": [ "network and internet security", "application and software security", "hardware security", "identity and access management", "cyber resilience and incident response" ], "related_models": [ { "relation": "is a kind of", "target": "information security", "why": "category" }, { "relation": "is a kind of", "target": "security", "why": "category" }, { "relation": "protects", "target": "integrated circuit", "why": "hardware" }, { "relation": "is related to", "target": "electronics", "why": "systems protected" } ], "identifiers": [], "standards_and_regulation": [ "ISO/IEC 27001 and NIST Cybersecurity Framework", "Data protection and breach notification laws", "Computer misuse and cybercrime laws" ], "failure_modes_and_hazards": [ "Breaches and data loss", "Facilitating attacks", "Security theatre without real protection" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "limits", "name": "Limits", "description": "Agent conduct.", "rationale": "Defensive only.", "layers": [ { "id": "authorisation", "name": "Authorisation", "description": "Authorised work.", "findings": [ { "id": "authorisation-finding", "name": "Authorisation", "description": "Authorisation.", "questions": [ { "text": "Is the request defensive, or does it seek to attack, access or disrupt systems without clear authorisation?", "kind": "boundary" }, { "text": "How should the agent decline unauthorised requests and support lawful security work?", "kind": "action" } ] } ] }, { "id": "incident", "name": "Incident", "description": "Active incidents.", "findings": [ { "id": "incident-finding", "name": "Incident", "description": "Incidents.", "questions": [ { "text": "Is a breach or attack under way?", "kind": "boundary" }, { "text": "Which immediate containment steps and reporting duties apply?", "kind": "action" } ] } ] } ] }, { "id": "protect", "name": "Protect", "description": "Practical security.", "rationale": "Basics first.", "layers": [ { "id": "individuals", "name": "Individuals", "description": "Personal security.", "findings": [ { "id": "individuals-finding", "name": "Individuals", "description": "Personal security.", "questions": [ { "text": "Which measures protect a person, such as strong authentication, updates and phishing awareness?", "kind": "provenance" }, { "text": "How can accounts be secured after compromise?", "kind": "action" } ] } ] }, { "id": "organisations", "name": "Organisations", "description": "Organisational security.", "findings": [ { "id": "organisations-finding", "name": "Organisations", "description": "Organisational security.", "questions": [ { "text": "Which controls and frameworks should an organisation of this size adopt?", "kind": "provenance" }, { "text": "How are risks assessed?", "kind": "action" } ] } ] } ] }, { "id": "threats", "name": "Threats", "description": "Understanding threats.", "rationale": "Know the risks.", "layers": [ { "id": "types", "name": "Types", "description": "Threat types.", "findings": [ { "id": "types-finding", "name": "Types", "description": "Threats.", "questions": [ { "text": "What are the main threat types, such as malware, phishing and ransomware, and how do defences address them?", "kind": "definition" }, { "text": "Which current advisories are relevant?", "kind": "provenance" } ] } ] }, { "id": "hardware", "name": "Hardware", "description": "Hardware and supply chain.", "findings": [ { "id": "hardware-finding", "name": "Hardware", "description": "Hardware security.", "questions": [ { "text": "What is hardware security, and why do supply chains matter?", "kind": "definition" }, { "text": "Which standards apply?", "kind": "provenance" } ] } ] } ] }, { "id": "govern", "name": "Govern", "description": "Standards and law.", "rationale": "Compliance.", "layers": [ { "id": "standards", "name": "Standards", "description": "Frameworks.", "findings": [ { "id": "standards-finding", "name": "Standards", "description": "Frameworks.", "questions": [ { "text": "Which security standards and certifications apply, and what do they require?", "kind": "provenance" }, { "text": "How is compliance audited?", "kind": "provenance" } ] } ] }, { "id": "law", "name": "Law", "description": "Legal duties.", "findings": [ { "id": "law-finding", "name": "Law", "description": "Legal duties.", "questions": [ { "text": "Which breach notification, data protection and cybercrime laws apply here?", "kind": "provenance" }, { "text": "Where can incidents be reported?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Should each subfield be a separate entry?", "How should advisories be linked?", "How should legal obligations be localised?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "abstract concept", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a computer security, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent explain computer security concepts and practices, help people and organisations protect systems and respond to incidents, explain standards and law, and decline requests to attack or compromise systems without authorisation.", "characteristics": { "substance": "abstract", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: cyber intelligence, cyber resilience, internet safety, hardware security, internet security, capability-based security, Group-IB Threat Intelligence, Group-IB Fraud Protection, Group-IB Managed eXtended Detection and Response, Group-IB Attack Surface Management, Group-IB Digital Risk Protection, Group-IB Business Email Protection.", "27 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 90 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a computer security, and on what evidence are they told apart?" ], "whatItIsMadeOf": "an abstraction with no physical instance", "physicalCharacter": [ "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Nothing to see. What is recognised is an instance of it, and which instances count is exactly what is argued about." ], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "cyber intelligence", "cyber resilience", "internet safety", "hardware security", "internet security", "capability-based security", "Group-IB Threat Intelligence", "Group-IB Fraud Protection", "Group-IB Managed eXtended Detection and Response", "Group-IB Attack Surface Management", "Group-IB Digital Risk Protection", "Group-IB Business Email Protection" ] } ], "standing": "Described in 90 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 27 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one computer security from another, and a computer security from things that resemble it.", "rationale": "Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.", "layers": [ { "id": "naming-and-identifiers", "name": "Names and identifiers", "description": "The names this thing goes by and the identifiers that survive translation and time.", "findings": [ { "id": "preferred-name-and-aliases", "name": "Preferred name, aliases and local names", "description": "Which name to use, which names mean the same thing, and which merely sound similar.", "questions": [ { "id": "preferred-name-and-aliases-q01", "text": "What identifies and describes the name of a computer security, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "preferred-name-and-aliases-q02", "text": "Who or what asserted this about the name of a computer security, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "preferred-name-and-aliases-q03", "text": "What may an agent decide or do once the name of a computer security is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "stable-identifiers", "name": "Stable identifiers and external keys", "description": "Identifiers that keep pointing at this kind of thing across systems and languages.", "questions": [ { "id": "stable-identifiers-q01", "text": "What identifies and describes an identifier for a computer security, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stable-identifiers-q02", "text": "Who or what asserted this about an identifier for a computer security, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stable-identifiers-q03", "text": "What may an agent decide or do once an identifier for a computer security is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "classification-and-granularity", "name": "Classification and granularity", "description": "Where a computer security sits among kinds, and how finely a task needs to cut it.", "findings": [ { "id": "kind-and-parents", "name": "Kind, parents and neighbouring kinds", "description": "The classes this thing belongs to and the ones it is next to.", "questions": [ { "id": "kind-and-parents-q01", "text": "What identifies and describes the kind of a computer security, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "kind-and-parents-q02", "text": "Who or what asserted this about the kind of a computer security, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "kind-and-parents-q03", "text": "What may an agent decide or do once the kind of a computer security is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "distinguishing-features", "name": "Distinguishing features", "description": "What separates a computer security from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a computer security, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "distinguishing-features-q02", "text": "Who or what asserted this about what distinguishes a computer security, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "distinguishing-features-q03", "text": "What may an agent decide or do once what distinguishes a computer security is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "state-and-lifecycle", "name": "State and lifecycle", "description": "The states a computer security passes through and the events that move it between them.", "rationale": "Most decisions about a thing depend on what state it is in now, which is a claim with a time on it, not a property.", "layers": [ { "id": "lifecycle-stages", "name": "Lifecycle stages", "description": "From coming into existence to ceasing to be one of these.", "findings": [ { "id": "stages-and-transitions", "name": "Stages and transitions", "description": "The stages worth naming and what moves a computer security between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a computer security, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stages-and-transitions-q02", "text": "Who or what asserted this about the lifecycle of a computer security, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stages-and-transitions-q03", "text": "What may an agent decide or do once the lifecycle of a computer security is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "observations-and-status", "name": "Observations and current status", "description": "What is observed about a computer security, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a computer security is recorded so that it can be superseded rather than overwritten.", "questions": [ { "id": "observation-record-q01", "text": "What identifies and describes an observation of a computer security, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "observation-record-q02", "text": "Who or what asserted this about an observation of a computer security, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "observation-record-q03", "text": "What may an agent decide or do once an observation of a computer security is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "definitions-in-contest", "name": "Definitions and who holds them", "description": "What computer security is taken to mean, and by whom.", "rationale": "When a field disagrees about a concept, the disagreement is the content. A model that picks one definition silently destroys the information.", "layers": [ { "id": "competing-definitions", "name": "Competing definitions", "description": "The main readings and the traditions behind them.", "findings": [ { "id": "definition-map", "name": "Definitions and their holders", "description": "Each definition with the school or body that holds it.", "questions": [ { "id": "definition-map-q01", "text": "Which definitions of computer security are in use, and which tradition or body holds each?", "kind": "definition" }, { "id": "definition-map-q02", "text": "What turns on the difference between them in practice?", "kind": "boundary" } ] } ] }, { "id": "operationalisation", "name": "Operationalisation", "description": "How it is measured or applied when it has to be.", "findings": [ { "id": "operational-record", "name": "Measures and proxies", "description": "Instruments and indicators used to stand in for it.", "questions": [ { "id": "operational-record-q01", "text": "How is computer security operationalised or measured in practice, and by what instrument?", "kind": "measurement" }, { "id": "operational-record-q02", "text": "What does that operationalisation leave out, and when does that matter?", "kind": "boundary" } ] } ] } ] }, { "id": "instances-and-use", "name": "Instances, use and consequence", "description": "What counts as an instance of computer security and what follows from calling something that.", "rationale": "Applying a concept is an act with consequences, so a model must say what the label licenses and what it does not.", "layers": [ { "id": "instances", "name": "What counts as an instance", "description": "Clear cases, borderline cases and non-cases.", "findings": [ { "id": "instance-tests", "name": "Tests for an instance", "description": "What would settle whether something falls under it.", "questions": [ { "id": "instance-tests-q01", "text": "What would settle whether something is an instance of computer security?", "kind": "boundary" }, { "id": "instance-tests-q02", "text": "Which borderline cases are argued about, and on what grounds?", "kind": "definition" } ] } ] }, { "id": "consequence", "name": "Consequence of application", "description": "Rights, duties or decisions that follow from the label.", "findings": [ { "id": "consequence-record", "name": "What the label licenses", "description": "What an agent may do once something is classified this way.", "questions": [ { "id": "consequence-record-q01", "text": "What follows practically once something is treated as computer security?", "kind": "action" }, { "id": "consequence-record-q02", "text": "What must an agent not infer from the label alone?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a computer security came from and when it held.", "rationale": "A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.", "layers": [ { "id": "source-and-authority", "name": "Source and authority", "description": "Who said it, on what evidence, and how strongly.", "findings": [ { "id": "claim-provenance", "name": "Claim provenance and confidence", "description": "The authority behind each claim about a computer security and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a computer security, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "claim-provenance-q02", "text": "Who or what asserted this about a claim about a computer security, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "claim-provenance-q03", "text": "What may an agent decide or do once a claim about a computer security is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "time-and-versions", "name": "Time, versions and supersession", "description": "When a claim was true, when it was learnt, and what replaced it.", "findings": [ { "id": "validity-and-supersession", "name": "Validity period and supersession", "description": "How an old claim about a computer security is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a computer security, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "validity-and-supersession-q02", "text": "Who or what asserted this about the validity of a claim about a computer security, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "validity-and-supersession-q03", "text": "What may an agent decide or do once the validity of a claim about a computer security is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 5, "layers": 10, "findings": 12, "questions": 32 } } } }