Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Background

...

Risk of low adoption with ripple effect of not gathering information needed to produce recommended ADs (e.g., ISACA members typically choose a certain set of ADs).

This risk can be mitigated by doing upfront research to validate:

a) members belonging to an organization share a list of common AD’s

b) create a mapping which shared AD’s match with which membership

Assumptions

Updates will be done in CCH in order to buy us time to get a more sophisticated solution UC 4.0

Assuming that users can choose to opt of choosing Affiliations or not choose since they might not want to fill out the information or might not belong to any affiliations.

...

User chooses Other for the industry which during the reporting won’t add much value.

Requirements

Requirement

User Story

Importance

Status

Comments

HubSpot data cleaned up to ensure all companies have Industry information populated from ZoomInfo.

P1

Not Started

It is a known issue that HubSpot industry data is imperfect. Approximately 200 accounts do not have industry assignment (demo 137, live 68).

We are relying on ZoomInfo - we can contract with a second organization to enrich data for those not enriched, however, we haven’t completed the AI mapping project to map industry lists between Zoom and other list types.

Within CCH, provide a means for the user to approve the enriched industry information or choose “other”.

P1

Not Started

Sean will provide more detail: individual users will not be allowed to update to the HubSpot Company Industry.

Within CCH, provide a means for the user to choose which affiliations they belong to such as ISACA, ICS2, HITRUST or others.

P1

Not Started

As example, marketing already has one set up for ISC2 Form (hsforms.com)

Initial list is:

  1. ISC2

  2. ISACA

  3. PCI

  4. SANS Institute

  5. EC-Council

  6. ISSA

  7. CSA

  8. OWASP

  9. HITRUST

  10. ISF

  11. SWIFT

  12. GRI

  13. OCEG

Within CCH, provide a means for the user to confirm which State-agency they belong to. This is only provided if the user’s domain corresponds to supported state agencies.

P1

Not Started

If not the domain, how else would we want the user to self-select or confirm which state-agency they belong to.

Provide a means of UCF super-administrators to identify which authority documents below to supported state-agencies.

P1

Not Started

Potential suggested solution, but engineering will consider other solutions: create a “dummy” company per supported state-agency and create a list of supported ADs.

Choice of Industry will be stored on the contact information in HubSpot.

P1

Not Started

Will optionally be stored in CCH if needed.

Choice of Affiliation(s) will be stored on the contact information in HubSpot.

P1

Not Started

Will optionally be stored in CCH if needed.

Choice of State-agency will be stored on the contact information in HubSpot.

P1

Not Started

Choice of Affiliation(s) will be stored on the contact information in HubSpot.

Periodically request users to re-update their information to ensure is up to date.

P3

Not Started

Cost

Estimated effort to fulfill all P1 requirements:

...