Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Discussion items

TimeItemWhoNotes
25-30 minAnything Urgent? Review the Kanban board?Team
  • Poppy CSP#3 has been released.  This includes the following fixes to several security-related issues:
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUIREQ-1082
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUICIRC-1060
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUICHKIN-422
  • John shared an update on requesting CSP approval for XSS-related issues in slack:
    • CSP proposal draft for XSS stories...any thoughts about this? Thinking this could copy/paste across those tickets to help with the process... just a simple bit of technical speak that PO's might not be interested in formulating themselves...
      FOLIO ui-modules occasionally need to render mark-up fed directly from our data stores. It is possible for these strings to contain javascript commands that can be executed when the string is interpreted and run by the browser. This fix filters those strings before they are actually presented by the browser, preventing any commands or script tags present from executingPassed language onto Khalilah and will do the same for Stephanie B.
  • We need to determine if DevOps can work on 
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyFOLIO-3896
     or if they don't have bandwidth, and the debian packages aren't used anymore, archive them.  It sounds like some SysOps do use this, but we know that DevOps has very little bandwidth these days.
    • Action:  Craig to ask in #devops if they can and are willing to work on this, then we can decide next steps.
  • Another prisma scan was done against the Q release candidate versions of modules.  Several issues were found and logged.
    • Some of these are related to the Architectural changes being proposed by the Eureka team.  Craig McNally will triage these with the team.
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.

  • 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.

Today:

Axel Dörrer to do a first draft as a base for further discussions


Status on pentesting works within Network traffic control group

Due to some absences on different reasons the group stalled. Axel will try to reactivate the group.

...