Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider changing the word "Attestations" to "Authenticity" #3

Open
santosomar opened this issue Dec 7, 2023 · 1 comment
Open

Comments

@santosomar
Copy link

I suggest replacing the term "attestation" with "authenticity." This change is recommended for the following reasons:

  • The term "attestation" may be confused with legal attestations of a company. ;-)
  • The term "authenticity" more accurately captures the essence of verifying the originality and integrity of AI components. It directly addresses the concern of ensuring that each element is genuine and unaltered, which is a fundamental aspect of AI security.
  • The concept of "authenticity" aligns closely with prevalent industry standards and practices in cybersecurity and AI development. This alignment can facilitate better understanding and compliance among practitioners and stakeholders.
  • While "attestation" generally refers to a self declaration or certification by a third party, "authenticity" is more aligned with integrity checks and provenance verification.

This issue was first raised in the previous AI BOM repository at https://github.com/manifest-cyber/ai-bom , but that repo was deleted.

@TheFoxAtWork
Copy link

Attestation has many meanings depending on the context. for instance, in the word of confidential computing, attestation is the proof of property of a system to a third party. IETF also has a definition in the context of its RATS architecture: https://www.ietf.org/archive/id/draft-ietf-rats-architecture-22.html

with that being said, attestations may be correct and appropriate since the attestation is a proof. Authenticity is proving who you are, and integrity is protecting the data from unauthorized changes. Both may be achieved by a singular function (such as verifying the signature and the resulting digest) but they are not always executed together (even though they should be).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants