VINCE is designed so that accounts are tied to individual users, and users can be made members of groups, most commonly a vendor group. So if you're part of a security team like a PSIRT, sign up as an individual and request to be added to the appropriate vendor group(s). An existing administrator for a vendor group can add you to the group.
Once you have created an individual VINCE account, ask us or a vendor group administrator. Users for whom we have existing trust (verified email address, possibly PGP key) are automatically associated with vendor groups. For users without existing trust, we perform a two-person validation process.
The first user added to a vendor group is granted the administrator role for that group. Our strong preference is that administrators manage further group membership. Multiple administrators are supported.
Each organization has a designated group administrator account. This account permits invitation to the organization's group, which in turn allows access to the organization's cases. If a group administrator is not set for your organization, send the CERT/CC a private message with the email address of the desired group administrator, and we will validate the change. If you are the group administrator, you may invite someone from the User Management Page by adding the new user's email address. This email address must match the email associated with the user's VINCE account. Users associated with an organization automatically have access to all of the organization's cases.
Not at this time.
Log out and back in to VINCE.
If a reporter is not participating in the case, it is possible that the reporter chose not to create a VINCE account. The CERT/CC also may not have contact information for the reporter, so it is possible that the reporter will not be involved in the case. If an unresponsive reporter is listed among the VINCE participants in the case discussion, the CERT/CC may encourage the reporter to respond (perhaps by reaching out directly to the reporter).
Once the CERT/CC has identified and added the vulnerabilities to the case, we will request the status and statement from each impacted vendor. At that time, you will be able to add a status (affected/unaffected/unknown) and an official statement from the case discussion page.
Anyone participating in the case can see your status and statement before we publish the vulnerability note. Once the CERT/CC publishes the vulnerability note, the public will be able to view your status and statement.
You can update your status and modify your statement from the case discussion page (the same place that you provided your original status and statement).
The CERT/CC will receive a notification when you update your statement. Once the CERT/CC views and approves the update, the changes will be reflected immediately on the published vulnerability note.
Contact information marked "public" will be shared with participants that require it, including reporters. Our eventual goal is to share contact information marked as "public" on our website so that it can be searched by the general public.
Use the "My Contact Info" page to edit your public contact information. Click "Edit My Contact Info" in the top right and toggle the "Public" switch to "Yes" to make specific contact information public. By default, all contact information that the CERT/CC has for your organization is set to "Not Public".
If you wish to receive a VINCE notification whenever another vendor receives a VINCE notification, you should contact the other vendor (outside of VINCE) and ask that vendor's VINCE Admin to add your chosen email address to their vendor contact information. Likewise, if you wish for another vendor to receive a VINCE notification whenever you receive a VINCE notification, then you should add an email address to your VINCE contact list that will reach that other vendor.