January 30, 2014 Meeting page: Difference between revisions

From IDESG Wiki
Jump to navigation Jump to search
m (4 revisions imported: Initial Upload of old pages from IDESG Wiki)
 
(No difference)

Latest revision as of 04:01, 28 June 2018

SECURITY COMMITTEE / FUNCTIONAL MODEL MEETING NOTES draft

Meeting Date: January 30, 2014

Attendees (see link to attendance and quorum calculation spreadsheet File:Sec Comm Member List 20140206.xlsx)

  1. Andrew Hughes
  2. Chan Lim
  3. Dave Brown
  4. Glenn Schoonover
  5. Michael Garcia
  6. Neville Pattinson
  7. Salvatore D’Agostino
  8. Suzanne Lightman
  9. Ryan Galuzzo

NOTES

  1. Roll call
  2. IPR policy reminder - https://www.idecosystem.org/system/files/filedepot/103/IDESG%20IPR%20Policy.pdf
  3. Review Agenda
    1. Accepted
  4. Nominations for Security Committee secretary
    1. None
    2. Weekly assigned note and minutes taker. Sal to start, if no volunteer Chair assigns person for that meeting.
  5. Review Functional Element Introduction review
    1. Mike to provide updated Introduction for general release.
  6. Discuss what do we want to complete and present at the next plenary
    1. Testing IDESG use cases against functional elements.
      1. Input from others IDESG stakeholders (management council, committees, plenary) on Functional Elements
      2. Consideration of other “elements” being proposed in other committees, groups, companies and pilots
    2. Potentially aspect of Security Evaluation Methodologies
  7. Review Functional Model plan (Adam will distribute)
    1. Not available
  8. Representative actions:
    1. Process/guidelines/templates to review/analyze against use cases, architectures, requirements, standards
      1. Agenda for next meeting
    2. Use case analysis approach – all use cases, some deep, in teams, one at a time
      1. Agenda for next meeting
  9. Other work collaborations – committees, frameworks, work products, standards, etc.
    1. Seek input on functional model elements
  10. Define Functional Model final deliverables
    1. Pending feedback on Functional Elements
  11. Other business
    1. None
  12. Review next actions
    1. Approve Functional Element material for release
    2. Focus on 6a and 8




Quick Links: Security Committee | Functional Model | Security Committee Meeting Notes | Security Committee Content