The CERT/CC is moving to a collaborative vulnerability coordination process because it is more efficient, it fosters goodwill and trust among those involved, and it consolidates relevant information into a single shared space. The change to a bus topology eases communication between parties when multiple vendors are involved, it lessens the requirement for a coordinator to be a moderator, and it increases speed of information transmission in multiparty vulnerability coordination efforts.
We encourage both vendors and reporters to make a VINCE account to facilitate active involvement in the coordination of vulnerabilities reported to the CERT/CC. A vendor without an account will be unable to view vulnerability reports shared with the CERT/CC or participate in the coordination process. A reporter without an account will be unable to communicate with vendors or receive updates on the coordination status of submitted reports. A reporter can create an account after submitting a vulnerability report to gain access to submitted reports, as long as the account is created using the same email address as the email address provided in the submitted report.
Vendors and reporters can expect a response from the CERT/CC within three days.
The CERT/CC considers the following conditions when deciding to coordinate:
More information on this topic can be found on our wiki.
The VINCE platform does not require PGP for secure communications. This was an intentional choice. While PGP email is a lowest common transport for coordination, PGP email is error-prone, especially at scale. VINCE relies on account authorization and access controls uses HTTPS to keep case discussions and messaging secure. VINCE users are still able to upload and share PGP keys on their contact pages.
We prefer that you message us through VINCE, but you may still email us at email@example.com. Please continue to use the appropriate tracking number (such as VU#, VRF#, or General-) in the subject of any email you send to us. Messages through the VINCE site will likely receive a faster response than email.
A direct private message sent to the CERT/CC by an individual user can be seen by the user and CERT/CC analysts. A direct private message sent from the CERT/CC to a vendor can be seen by CERT/CC analysts and all members of the vendor organization with associated VINCE accounts.
Anyone participating in the case can see the posts in the case discussion. Additionally, any participants that are added after discussion has begun will have access to the full discussion forum, including previous posts that occurred before the new participants joined the discussion. All coordinators, vendors, and participants are listed on the left-hand side of the case view.
No, you are unable to direct private-message another VINCE user. We encourage all relevant case discussion and coordination to happen within VINCE's case discussion page.
VINCE currently only supports one Coordinator role, and that Coordinator is the CERT/CC. Looking outside of VINCE, a vulnerability coordination case can have more than one coordinator. VINCE does support the addition of other Participants to a case, these Participants can be other trusted researchers or experts or members of a different coordination team than the CERT/CC.
VINCE operates in UTC. Currently, all dates and times are also shown in UTC. We intend to make this configurable on a per-user basis, and probably also shift to the ISO 8601 time and date format.
Please see the API section of the User Manual.