Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Attendees:
Present: Jay Alameda, Shawn Strande, Cindy Wong, John Towns, Dina Meek, Lavanya Podila, Kim Bruch, Shannon Bradley, Lisa Kaczmarczyk
Decisions made during the meeting:
Use Decision Macro
Agenda/Notes
Fate of Conference Competitive Analysis (CBE & Comms) - Jay, Dina, Kim
Prioritizing different conferences - traditional + other suggested ones
Which conferences should be our audience?
Wanted to have list done by February
Where does this task set going forward?
Review Action Items
Review Metrics Spreadsheet
Should any other Metrics information be pulled from anywhere else?
Following up on MFA for Confluence/JIRA
Shortened text for email to EC needs approved
We have had a request from ACCESS Cybersecurity to add Multi-Factor Authentication/Two Factor Authentication to Confluence and JIRA.
This is being proposed so we can do our best to eliminate unauthorized access resulting from disclosure or compromise of reusable passwords (which remains the most common source of intruder access). So far, we have not had a problem with this in JIRA/Confluence, but it would be nice to be prepared in advance of any attempted intrusions.
Effects on User Experience:
For public access sites/pages/documents, there should not be any difference in user experience, as no accounts nor authentication are required.
For sites/pages/documents that currently require a user to be authenticated for access, this would be an additional step to complete authentication.
Some Initial Plans for Implementation:
We will need to create a test site to try things on before we roll out a configuration change that affects everyone
We'll want to document what people can expect to see when the change is put in place
We will need instructions on what they may have to do to update their login preferences to add TFA
Updates
Comms Plan approved; charter?
Web Presence - Dina developing a plan for feedback; charter to be updated based on this
Lavanya Podila Shannon Bradley
Risk Register Review - Change Tracking Summary Report
Based on discussion with NSF yesterday - wondering about how we communicate regarding changes in risks.
To improve visibility re: Risks and other team updates / changes - I have changed the view of the summary risk report
I suggest we add a segement segment to this meeting where we review the risks that have been updated since our last meeting
We can then reach out to teams when we feel there are opportunities to discuss how certain risks impact other teams or the project as a whole.
Info |
---|
Parking Lot |
Next Meeting: 31st January 2024
Action Tracker:
Use Action Item Macro to track assigned To Do Items - check the box when it is complete
Reference