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

[CTF] Develop Content Trust Framework #2

Open
joofio opened this issue Nov 24, 2023 · 5 comments
Open

[CTF] Develop Content Trust Framework #2

joofio opened this issue Nov 24, 2023 · 5 comments
Assignees
Labels
MVP3 Issue to be delivered in MVP3
Milestone

Comments

@joofio
Copy link
Contributor

joofio commented Nov 24, 2023

No description provided.

@joofio joofio added the MVP3 Issue to be delivered in MVP3 label Nov 24, 2023
@margoraja
Copy link

margoraja commented Nov 24, 2023

Just to be clear:
We are developing content trust that focuses on data integrity aspect. It remains usable as a module of CTF once evaluation and certification by UPM, which in essence should apply data integrity protection upon the certification results and etc.

@joofio
Copy link
Contributor Author

joofio commented Nov 29, 2023

can you explain further the part of " It remains usable as a module of CTF once evaluation and certification by UPM,"? It was not clear to me

@amedranogil amedranogil added UI/UX and removed UI/UX labels Dec 5, 2023
@amedranogil amedranogil moved this from Todo to In Progress in MVP Issues Dec 5, 2023
@amedranogil amedranogil added this to the MVP3.1 milestone Dec 12, 2023
@amedranogil
Copy link

I think @margoraja is referering to the trust function which is the the layer that uses the data integrity layer to provide a level of trust understandable by other components and even users.

I was just looking a the provenance FHIR IG, which is the basis for CTF, I saw that currently "activity" which is the action the provenance record is about has many options (see https://terminology.hl7.org/5.4.0/CodeSystem-iso-21089-lifecycle.html ) however amongts these there isn't one which I could definitelly say it should be used by regulators to certify conent, maybe "attest", maybe "verify"?

Maybe what we need is to close the specification for CTF, identify which actions and by who can be taken and map all this. This definition may be extended in the future, but this will definitelly help explain and exploit the component as envisioned.

@amedranogil
Copy link

amedranogil commented Apr 11, 2024

There are 3 components:

  1. Integrity
  2. provenance Engine
  3. Trust Function manager

First is developed by @margoraja and the other 2 by UPM, but they are dependent on 1.
What is the current status?

@margoraja
Copy link

That is correct. Integrity (resource and/or provenance record signing) has been developed, provenance and tf manager most likely are dependant on it as well.
Integrity itself is capable of signing the whole resource and/or provenance record within the resource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MVP3 Issue to be delivered in MVP3
Projects
Status: In Progress
Development

No branches or pull requests

3 participants