Page Comparison

• Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key SECURITY-9

  • 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.  
    • folio-spring-system-user is used for login API calls. 
    • We should probably ask that edge-common-spring is updated to remove the dependency on folio-spring-system-user.
      • Craig McNally  will follow up with Taras and get the story created...  Also ask about the other modules (dematic, caiasoft, etc.) see below.
  • Axel Dörrer will do the same for the other 4
    • Has created some, e.g.

      Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODCON-114

    • mod-caiasoft, edge-dematic, edge-inn-reach, edge-dcb still don't have JIRAs.
      • We need to figure out if the SYSTEM_USER_NAME specified in application.yaml is actually used, or if it can be removed.
      • See comments above about removing folio-spring-system-user dependency from edge-common.

Anything we want to discuss here?  Do we want to get additional details from Peter?  Invite him to discuss next week?

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.  
    • This could mean either:
      • Explicitly encrypting/decrypting in the application layer and storing the encrypted data in postgres
      • Utilizing postgres extensions/modules to encypt certain columns, e.g. via pgcrypto (see https://www.postgresql.org/docs/current/encryption-options.html)

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.