Versions Compared

Old Version 1

changes.mady.by.user John Coburn

Saved on

compared with

New Version Current

changes.mady.by.user John Coburn

Saved on

Key

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

Date

Feb

Attendees

NamePresentPlanned Absences

Craig McNally 

yes
Julian Ladisch 
yes

Axel Dörrer 



Ryan Berger 


Chris Rutledge 

yes

Jakub Skoczen 

yes
John Coburn 
yes

Skott Klebe 






...

TimeItemWhoNotes
25-30 minAnything Urgent? Review the Kanban board?Team
  • Our kanban board has a swimlane for "no team assigned".  There's only one Jira there which is essentially a test issue.  I don't see an option for setting the development team on that particular issue.  We need someone to investigate.
  • John to create Jira ticket for centralized component which can be used to resolve UICIRC-106 & STSMACOM-816 
    • This is done, and linked to these JIRAs - see 
      Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keySTCOM-1270
    • Initial solution includes the DOMPurify library https://github.com/cure53/DOMPurify
    • The work is in progressmerged for stripes-smart-components. STSMACOM-816
    • After testing, - possibly for Ramsons release - we can switch to centralized functionality making use of DOMPurify.
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

Axel Dörrer 

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

...