Skip to end of banner
Go to start of banner

2023-11-09 Meeting notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Date

Attendees

NamePresentPlanned Absences

Craig McNally 

Y
Julian Ladisch 


Axel Dörrer 



Ryan Berger 


Chris Rutledge 



Jakub Skoczen 



John Coburn 


Skott Klebe 






Discussion items

TimeItemWhoNotes
?Anything Urgent? Review the Kanban board?Team
  • SECURITY-9 - Getting issue details... STATUS
    • Craig McNally  will investigate/reach out to devs for:  edge-courses, edge-fqm, and mod-consortia
      • Created story for mod-consortia and linked it to SECURITY-9
      • edge-fqm/edge-courses:  the edge-common-spring framework apparently has a runtime dependency on the folio-spring-system-user library (due to dependency injection?).  I've reached out to Taras to see what we can do about this, but he's on vacation.  Circle back next week.
        • No update from Taras yet.  Craig McNally will check with him and report back in Slack.
    • Axel Dörrer will do the same for the other 4
      • Has created some, e.g. MODCON-114 - Getting issue details... STATUS
      • mod-caiasoft, edge-dematic, edge-inn-reach, edge-dcb still don't have JIRAs.
<5 minConfluence Security Issue (Ransomware)Team
Anything we want to discuss here?  Do we want to get additional details from Peter?  Invite him to discuss next week?
Time permittingAdvice for handling of sensitive banking informationTeam

From slack conversation, I think I've gathered the following:

  • In this case (bank account and transit numbers), the information is highly sensitive.  
  • Highly sensitive information should:
    • Be stored in it's own table
    • Accessed via a dedicated API
    • Protected by a dedicated permission
    • Encrypted in the database, not only on disk.  

Let's review and discuss before providing this feedback to Raman.

Axel Dörrer also suggested that defining classes of sensitivity could help teams determine which techniques are applicable in various situations.  I agree having some general guidelines on this would be helpful.

  • regular data
  • low sensitive - permission based on same API
  • high sensitive - permission based on dedicated API

It would probably help to provide concrete examples of data in each class.  This can be a longer term effort, we don't need to sort out all the details today.

Today:

  • Next Steps:
    • Clearly define/formalize the various classes
      • Come up with concrete examples of each class
    • Build out guidance
      • Come up with concrete examples of how to protect each class of data.
    • Consider storing some classes of data outside of postgres altogether - e.g. in secret storage.
      • What would be the guidance we provide to teams for this so we don't end up with each team doing things differently?
      • SecretStore interface and existing implementations are currently only read-only.  They would need to be extended to allow for creation/mgmt of this information.
    • Craig to start a conversation in slack about this.
      • Seeking a volunteer to generate a draft document for us to review at a later meeting.

Action items

  •  


  • No labels