computer security
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.
Bundle → Layer → Finding → Questions Filled
4 bundles · 8 layers · 8 findings · 16 questions
Limits Agent conduct.
Authorisation
Authorised work.
Authorisation
Authorisation.
- Is the request defensive, or does it seek to attack, access or disrupt systems without clear authorisation? boundary
- How should the agent decline unauthorised requests and support lawful security work? action
Incident
Active incidents.
Incident
Incidents.
- Is a breach or attack under way? boundary
- Which immediate containment steps and reporting duties apply? action
Protect Practical security.
Individuals
Personal security.
Individuals
Personal security.
- Which measures protect a person, such as strong authentication, updates and phishing awareness? provenance
- How can accounts be secured after compromise? action
Organisations
Organisational security.
Organisations
Organisational security.
- Which controls and frameworks should an organisation of this size adopt? provenance
- How are risks assessed? action
Threats Understanding threats.
Types
Threat types.
Types
Threats.
- What are the main threat types, such as malware, phishing and ransomware, and how do defences address them? definition
- Which current advisories are relevant? provenance
Hardware
Hardware and supply chain.
Hardware
Hardware security.
- What is hardware security, and why do supply chains matter? definition
- Which standards apply? provenance
Govern Standards and law.
Standards
Frameworks.
Standards
Frameworks.
- Which security standards and certifications apply, and what do they require? provenance
- How is compliance audited? provenance
Law
Legal duties.
Law
Legal duties.
- Which breach notification, data protection and cybercrime laws apply here? provenance
- Where can incidents be reported? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Cross-cutting context
- Entry kind
- thing
- Plane
- XCT
- Domain
- XCT.STA
- Other names and narrower kinds
- 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
What it is Filled
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.
Why it exists Filled
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.
Distinguishing features Filled
- Protects confidentiality, integrity and availability
- Technical and human measures
- Standards-based
- Legally regulated
What robots and AI may and may not do Filled
Must not
- Access, scan or test systems without the owner's authorization.
- Assist in creating malware, exploits or attacks against systems it is not authorized to test.
- Disable logging, monitoring or security controls to hide activity.
- Disclose vulnerabilities publicly before the owner has had a fair chance to fix them.
Only with a human decision
- Shutting down or isolating production systems during an incident.
- Authorizing a penetration test or disclosing a vulnerability.
May
- Monitor, patch and harden systems the agent is authorized to administer.
- Explain security practices and report vulnerabilities to the owner of the affected system.
Moral aspects Filled
- Breaches expose personal data and can stop hospitals, utilities and services.
- Security monitoring can itself intrude on staff and users' privacy.
Who is affected
- Users whose data is held
- Organizations and their staff
- People relying on critical services
Owners Filled
Steward
The owner or operator of each system; security teams and regulators oversee it.
Master systems
- Vulnerability databases
Links to other meta-models Filled
parent
- Q1067601 - registry parent class
- Q189900 - registry parent class
- Q2526135 - registry parent class
related
- information security - category
- security - category
- integrated circuit - hardware
- electronics - systems protected
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.computer-security
- Wikidata: Q3510521 (https://www.wikidata.org/wiki/Q3510521)
Direct properties not applicable Not applicable
Not applicable
Plane XCT: no invented physical properties.
Recognition optional Filled
- Defensive measures and controls
- Standards and audits
- Attacking systems without authorisation is a crime, not security
- Not physical; practices, controls and policies.
Capabilities and actions required Filled
- explain threats and defences
- give practical security guidance
- support incident response and reporting
- explain standards and legal obligations
Hazards and failure modes required Filled
- Breaches and data loss
- Facilitating attacks
- Security theatre without real protection
Standards and interfaces required Filled
- ISO/IEC 27001 and NIST Cybersecurity Framework
- Data protection and breach notification laws
- Computer misuse and cybercrime laws
Context of use required Filled
- Protecting systems and data.
- network and internet security
- application and software security
- hardware security
- identity and access management
- cyber resilience and incident response
Sources Filled
- Wikidata item Q3510521: computer security - identity and sense of the item
- Wikipedia: Computer security - general description of the item
Open questions
- Should each subfield be a separate entry?
- How should advisories be linked?
- How should legal obligations be localised?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q3510521/spec.json