Token Trust & Traceability WG

Tuesday 31 Mar 2026, 15:00 → 16:30 Europe/Zurich

Fortnightly for the risk assessment season.

 

https://codimd.web.cern.ch/dzLwpLEYQ2WxWScRtcheGg#

 

# TTT 31st March 2026

Attending: Matt, Donald, TomD, Luna, Maarten, Linda, DaveK

## Actions, From last meeting
- continue work on document
- Tom to make a start on CHEP

## Token Issuer CA Concerns
https://indico.cern.ch/event/1668475/

I don't think we need to add more today, other then to make this is an on going concern.

This is the CA of the certificate of the issuers - currently these are non-IGTF for many token issuers.

Issue came to light after DUNE campaign, as they use an Amazon certificate. The way to configure this on ARC CEs was problematic.

Should we take this into account for this risk assessment? ML reckons we don't. The "cracks" can only be exploited if issues in code base

Implicitly assumed token issuers run "properly".

Know that configuration errors are made, and only found via "negative testing". Only CMS explicitly doing this at the moment.

Would likely raise more questions, especially as we need to generalise from ARC CE.

Can make a different decision for a future version of the document.

MD - agree not to mention in current version, as came up post "freezing".

ML reframes the ARC issue for others.

Luna notes that this directly isn't a token issuer, as ML notes the issue is the certicate branch.

ML - bigger analysis of services being misconfigured (last time we did this is in the report by Romain that we linked). Focussing on tokens for this risk.

Previous assumptions of IGTF CAs as a bedrock, we would be hollowing this out. Need to avid the slippery slope.  
During meeting on Friday found a few possible ways forward. Maarten will forward the notes. Recipes can be given to ARC devs and to sites.  

 

## CHEP presentation
Focussed on the process, rather then the results. TomD to set things going post Easter.

CHEP will be "inverse" of this one,  heavy methodogy.

 

## Continuing the risk document
Notes from last time:
- meta table becomes table - done
- move executive summary up, give scoring information to it - done
- add in a "Methodology section" - done
- remove template page -done

** To-Do: adjust the impact table according to some conversation
** Scan through the document step by step?

Most of technical details decided on. 
--worked through the comments, solving all but one (from Luna, to be cleaned up)

--version table under title? Seems sensible. Will look at a way of doing this.

PDF version of the document will become the "official" version.

Links to sections in the table.

Do we want a reference section?  
It would be a good as a way of finishing the document.  

## Actions
Anyone interested read through the document and comment. All technical information should already be in there. Can update later in version 1.1

For next meeting have a pdf prototype version ready.

## AOB, Next meeting
Next "standard phase" TTT would be 14.00 CEST on Tuesday 14th April (with the one after that being the 28th).

ML will only be able to make from 14.30, but should be fine for a meeting as hopefully it will be short and we'll have a PDF version to show off.

Have a good Easter break!

1 Actions, Since Last Meeting

2 Discussion: Risk Analysis

Inspiration may be taken from these assessments from EGEE and WLCG done many years ago:

• EGEE
• WLCG

Work through the Workflows added by Maarten to the document, and review the scoring methodology.

Continue discussion from the list.

3 Discussion

Probably just continuing the above.

https://github.com/TTT-WG/TTT-WG/issues

4 AOB, next meeting

Meeting again on the 31st?