Page MenuHomePhabricator

Security Readiness Review For Diff Calendar
Closed, ResolvedPublic

Description

Project Information

Description of the tool/project: Movement Communications is looking to add a community calendar to Diff. Ideally, users would be able to login (using their Wikimedia credentials via oAuth) and add an event to a centralized calendar.

Description of how the tool will be used at WMF:

We'd like to use an existing WordPress plugin to give us the ability to have a calendar of events. This plugin has a "Pro" version we would license for additional features and support. It's called The Events Calendar (https://theeventscalendar.com).

Dependencies

List dependencies, or upstream projects that this project relies on.

https://github.com/the-events-calendar/the-events-calendar

Has this project been reviewed before?
No.

Working test environment
https://blog-wikimedia-org-develop.go-vip.net/events/

Post-deployment
Movement Communications - Chris Koerner

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Jcross added subscribers: Dsharpe, Jcross.

Sending over to @Dsharpe as a supplier assessment. David, please let me know if we should send these your way via some other workflow?

sbassett triaged this task as Medium priority.
sbassett added a project: SecTeam-Processed.
sbassett moved this task from Incoming to In Progress on the Security-Team board.

Hello @CKoerner_WMF ! My understanding ready through this task is that we haven't bought anything from https://theeventscalendar.com/ yet. If the Foundation decides to do so, then when that spend flows through Coupa it should be marked as a SaaS-related request and automatically trigger a vendor security review. I haven't seen anything about this purchase in Coupa. Did I miss something?

@Dsharpe You haven't missed anything. We didn't know if it was best to alert you before we made any purchase as we didn't want to buy something only to have Security say no. If it's normal to proceed as you describe I can talk to my supervisor to make that happen.

Yes, it is the current process for most things. We'll jump in as part of the Coupa process (for SaaS-related vendors only right now) because we don't have the capacity to review potentially several vendors for every initiative across the Foundation. Once a team has progressed far enough to where they are ready to buy, then we take a look. The Coupa process might also, depending on what is being purchased, kick off other helpful reviews by Legal and Privacy.

For screening vendors, meaning as you whittle your list of possibilities down to just one, folks can use https://office.wikimedia.org/wiki/Security/Guides/Supplier_and_Provider_Initial_Risk_Assessment_Questions. If a vendor doesn't have answers for those items available on their website, it normally helps to ask about at least those 12 items to see how the vendor responds. People doing privacy reviews might ask more, but those 12 questions are a good start for the vendor security review side of the process.

If you decide to proceed, we'll catch this request as it flows through Coupa (please make sure to mark "yes" for "Is this a SaaS request, and that will cause our part of the review process to start).