computer program
Let an agent handle programs by function, version, platform, licence, security and provenance, and never help create or deploy malicious software.
Bundle → Layer → Finding → Questions Filled
4 bundles · 8 layers · 8 findings · 16 questions
Identity Which program.
Name and version
Release.
Release
Name and version.
- Which program and version is it? provenance
- Who publishes it? provenance
Integrity
Signatures and hashes.
Integrity
Integrity checks.
- Is the download signed, and does the hash match? boundary
- Is the source official? provenance
Function What it does.
Purpose
Features.
Purpose
What it does.
- What does the program do? definition
- On which platforms does it run? definition
Data use
Permissions and privacy.
Data
Data handling.
- What data does it collect? boundary
- What permissions does it need? boundary
Security Vulnerabilities and malware.
Vulnerabilities
Known issues.
Vulnerabilities
Known vulnerabilities.
- Are there known vulnerabilities in this version? provenance
- Is a patch available? action
Malware
Harmful software.
Malware
Malware limits.
- Is the request about creating or deploying malware? boundary
- How should the agent respond, for example with defensive guidance? action
Licensing Rights.
Licence
Terms.
Licence
Licence terms.
- Under which licence is it distributed? provenance
- What does the licence allow? boundary
Support
Maintenance.
Support
Support status.
- Is the program still supported? boundary
- When does support end? measurement
Classifiers Filled
- Family
- Thing Registry
- Category
- Information and virtual systems
- Entry kind
- thing
- Plane
- INF
- Domain
- INF.MED
- Other names and narrower kinds
- computer poker player, cloud storage app, virtual instrument, ransomware, Platforms Code, ransomware as a service, REvil, Cursynth, bitcoin wallet, dating app, social media app, Vim plugin
What it is Filled
A set of instructions that a computer can execute to perform tasks, from applications and utilities to games, virtual instruments and malicious software such as ransomware.
Why it exists Filled
Let an agent handle programs by function, version, platform, licence, security and provenance, and never help create or deploy malicious software.
Distinguishing features Filled
- Executable instructions
- Versioned and licensed
- Security depends on provenance and updates
- Malware is software used to harm
What robots and AI may and may not do Filled
Must not
- Write, spread or run malicious software such as ransomware or spyware.
- Install or run a program on a system without its owner's authorization.
- Copy or distribute a program in breach of its licence.
- Disable security updates or protections on systems others depend on.
- Hide what a program does from the people who run it.
Only with a human decision
- Deploying a program to production systems or many users at once.
- Running code from an untrusted source.
May
- Run, test and update programs on systems it is authorized to administer.
- Explain what a program does and report bugs to its maintainers.
- Check software licences before copying or distributing a program.
Moral aspects Filled
- Programs decide matters that affect people, so faults and hidden behaviour cause real harm.
- Malicious software holds hospitals, schools and people to ransom.
Who is affected
- Users of the program
- Owners of systems it runs on
- People affected by its decisions
Owners Filled
Steward
The author or licensor holds the rights; the operator answers for each installation.
Links to other meta-models Filled
parent
- Q11491547 - registry parent class
- Q4303335 - registry parent class
related
- computer - platform
- software licence - rights
- cryptographic key - security
- work - creative and technical work
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.computer-program
- Wikidata: Q40056 (https://www.wikidata.org/wiki/Q40056)
- package name and version: semantic version identifies releases
- CPE name: cpe:2.3 string vulnerability databases
- hash: SHA-256 file integrity
Direct properties not applicable Not applicable
Not applicable
Plane INF: no invented physical properties.
Recognition optional Filled
- Name, version and publisher
- Code signatures and checksums
- Malware disguises itself as legitimate software
- Files, app icons and interfaces; source code in text.
Capabilities and actions required Filled
- install and run it
- update and patch it
- license it
- audit its security
Hazards and failure modes required Filled
- Vulnerabilities and exploits
- Malware and ransomware
- Supply chain attacks
- Licence violations
Standards and interfaces required Filled
- EU Cyber Resilience Act
- Copyright and software licences
- Computer misuse law
Context of use required Filled
- Making computers do useful work.
- applications
- system software
- games
- virtual instruments and plug-ins
- cloud services and apps
- malware such as ransomware
Sources Filled
- Wikidata item Q40056: computer program - identity and sense of the item
- Wikipedia: Computer program - general description of the item
Open questions
- Should software types be separate entries?
- How should versions and vulnerabilities be linked?
- How should agents refuse malware requests consistently?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q40056/spec.json