ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
2
Risk Assessment Worksheet
3
4
No.RISKToIP LAYERYoma ValuesTRUST AREAS AFFECTEDSEVERITYLIKELIHOODRISK IMPACTRISK CONSIDERATION ACTIONSRISK TREATMENTRISK TREATMENT ACTIONSRESIDUAL RISK
5
Administering Authority Risks
6
Lack of competence to perform roleEcosystemTrustGovernance45HIGHNeed for experienced personnel, proper training and governance frameworkAcceptanceThere is no GA, however there IS a mechanism in REVISIONS section of the GF for changing and updating the GF which is managed by the Administering Authority
7
Lack of a dispute resolution processEcosystemTrustGovernance41LOW-MEDIUMNeed for a mechanism for complaints and dispute resolution within the Yoma community (ie when it is not a matter of breaking law e.g. a contract)AvoidanceAdded to the Governance Framework - ADR process in governance requirements controlled document
8
Lack of sufficient policy and practicesEcosystemTrustGovernance23LOW-MEDIUMNeed for complete governance framework and revisions scheduleAvoidanceGF written and includes revisions section, already have key practices in place (e.g. privacy policy)
9
Lack of consistency in operating practices of roles, especially in transition between taskforce, interim GA and new yoma entities in the futureEcosystemCommunityGovernance43MEDIUMRequires proper oversight and trust assurance mechanismsOtherClauses in the GF which include a requirement on the AA and the YPM to carry out 6 monthly risk assessment process and to have in place a data breach emergency plan.
10
Lack of accountability of roles in networkEcosystemCommunityGovernance52MEDIUMRequires proper oversight and trust assurance mechanismsOtherResolved partly because all participants have a role as a Yoma Member alongside other roles therefore offering consistent set of rights and duties to eachother. Also RA process requirements
11
Lack of communication about governance practicesEcosystemTrustGovernance22LOW-MEDIUMRequires appropriate communication channelsAvoidanceWithin GF there are requirements to publish including related to revisions and extensions, also the GF itself clearly publishes the policies & practices
12
Lack of appropiate authority (For Interim GF, there is no GA)EcosystemTrustGovernance22LOW-MEDIUMRequires recognition and endorsement by relying partiesOtherAlready have administering authority & YPO and mechanisms for changing the GF - therefore AA should be all that is necessary
13
Ineffective bias in authorityEcosystemFairnessGovernance32LOW-MEDIUMRequires even representation, voting standards and non-discrimination practicesAvoidanceAll parties become Yoma members, all are therefore subject to common rules of the game.
14
Lack of Relying Party (Any entity within the yoma ecosystem, subject to the Yoma Governance Framework) recognitionEcosystemTrustGovernance43MEDIUMRequires recognition and endorsement by relying partiesAcceptanceIn future a Trust Registry may be put in place, until then mitigations from local yoma community growth approach
15
Ecosystem Lacks Jurisdictional AcceptanceEcosystemTrustGovernance11LOWRequires Mapping of Jurisdictional RegulationAvoidanceHas been accepted and operational in SA since 2020
16
Ecosystem Lacks Industry AcceptanceEcosystemPersonal Self-DevelopmentGovernance21LOWRequires Mapping of Industry RegulationAcceptanceNot really a risk for Yoma
17
Ecosystem Issues Trust Marks Inappropriately or Without BasisEcosystemGovernanceRequires Adequate Trust Marks Policies
18
Ecosystem Allowing Inappropriate Actors to Participate in NetworkEcosystemTrustGovernance43MEDIUMRequires Provider Evaluation and Acceptance ProcessesAvoidanceCurrent mitigation is small group of trusted partners, accept this risk because access for youth participants is the priority
19
Ecosystem Inappropriately Blacklisting or White Listing Other EcosystemsEcosystemCommunityGovernance22LOW-MEDIUMRequires Adequate Ecosystem Black and White Listing ProcessingAvoidanceClear Revisions & Extensions policy and process which includes Yoma community review and pubic review cycles
20
Issuer Risks (Opportunity Provider, yoma platform operator)
21
Credential Issued without sufficient basisCredentialTrustData Integrity52MEDIUMRequires training, trust assurance practices and controlled practicesTransferenceCurrently all credential issuance carried out by Yoma platform
22
Credential Issued before appropriate proofing of basisCredentialTrustData Integrity51LOW-MEDIUMRequires training, trust assurance practices, controlled practices and proper workflowAcceptance
23
Credential Issued in the wrong format or structureCredentialTrustData Integrity51LOW-MEDIUMRequires standard formats and formatting controlsAcceptance
24
Credential issued to impostorsCredentialTrustSecurity54HIGHRequires Trusted Issuers, trust assurance practicesAcceptancePlan is that they will have in the future with some ID&V issued with Yoma Member Credential. Thereafter will just be the Opportunity Provider to issue to the correct individuals.
25
Credential Lacking UniquenessCredentialPersonal Self-DevelopmentData IntegrityLOWRequires Appropriate Credential SearializationAcceptance
26
Credential Becoming ObsoleteCredentialPersonal Self-DevelopmentData Integrity34MEDIUMRequires Appropriate Credential Validity PeriodsAcceptance
27
Lack of Credential RevocationCredentialFairnessData Integrity55HIGHRequires Adequate Credential Status Checking ProceduresAcceptanceImplement revocation
28
Identity Proofing Practices Inadequate for Level of AssuranceCredentialTrustData IntegrityLOWRequires Ecosystem Governance Conformance ProceduresAcceptance
29
Issuer Practices Not Accepted by Ecosystem EcosystemTrustGovernance11LOWRequires Issuer Practice Conformance ProceduresAvoidanceIn future Issues will be verified before being accepted as opportunity providers int he system. Issuer and Verifier registry to be created in the future. Currently Yoma Platform Operator are only issuer
30
Issuer Operations UnavailableCredentialTrustAvailability23LOW-MEDIUMRequires Network Redundancy ProceduresAcceptance
31
Verifier Risks (Employment Opportunity Provider, Token Provider)
32
Lack of competence to perform roleCredentialTrustGovernance45HIGHNeed for experienced personnel, proper training and governance frameworkAcceptanceDevelop training / information for verifiers
33
Lack of consistent verification practicesCredentialFairnessData Integrity44MEDIUM-HIGHRequires training, trust assurance practices and controlled practicesAcceptanceWithout LEI as part of issuer on-boarding process risks around issuer reliability
34
Missing verificationCredentialTrustData IntegrityLOWRequires training, trust assurance practices and controlled practicesAcceptance
35
Untimely verificationCredentialTrustData Integrity24MEDIUMRequires time-based controlsAcceptance
36
Evidence of verification incomplete or in incorrect formatCredentialPersonal Self-DevelopmentData IntegrityLOWRequires standard formats and formatting controlsAcceptance
37
Verifier Practices Not Accepted by Ecosystem EcosystemTrustGovernance52MEDIUMRequires Verifier Conformance ProceduresAvoidanceNo verifiers at present
38
Suspended Credential Being Accepted N/ACredentialTrustData Integrity54Requires Adequate Credential Suspension Processes
39
Revoked Credential Being AcceptedCredentialTrustData Integrity34MEDIUMRequires Adequate Credential Status Checking ProceduresAcceptance
40
Man-In-The_middle Attack During Legitimate VerificationCredentialTrustSecurityLOWRequires Verifier Vulnerability PracticesAcceptance
41
Verifier Network UnavailableCredentialTrustAvailability24MEDIUMRequires Network Redundancy ProceduresAcceptance
42
Authoritative Issuer Registry Risks LOW
43
Lack of competence to perform role (Resources; validation and issuer on-boarding, revalidation) Human resources & business processes.CredentialTrustGovernance35MEDIUM-HIGHRequires Issuer Practice Conformance ProceduresAvoidanceUsing common standards that although innovative are not risky tech and performed by competent individuals in YPO
44
Unavailable registryCredentialTrustAvailability35MEDIUM-HIGHRequires availability controlsAcceptanceImplement Trust Registries
45
Lack of appropriate access to registryCredentialFairnessSecurity35MEDIUM-HIGHRequires appropriate access controlsAcceptanceImplement Trust Registries
46
Inapproriate access writes to registryCredentialFairnessData Integrity35MEDIUM-HIGHRequires appropriate access management controlsAcceptanceImplement Trust Registries
47
Breach of registryCredentialTrustSecurity55HIGHRequires appropriate security perimeter, breach detection and notification controlsAcceptanceImplement Trust Registries
48
Exploited Use of Stolen CredentialsCredentialTrustData Integrity55HIGHRequires Adequate Breach Notifiaction ProcessesAcceptanceImplement Trust Registries
49
Credential Registry Not Accepted by Ecosystem EcosystemPersonal Self-DevelopmentGovernance52MEDIUMRequires Credential Verifier Conformance ProceduresAvoidanceAdded Trust Registry requirements to information trust requirements controlled document
50
Authoritative Schema Registry Risks
51
Lack of competence to perform roleCredentialTrustGovernance32LOW-MEDIUMRequires Issuer Practice Conformance ProceduresAvoidanceUsing common standards that although innovative are not risky tech and performed by competent individuals in YPO
52
Unavailable registryCredentialTrustAvailabilityLOWRequires availability controlsAcceptanceImplement Trust Registries
53
Lack of appropriate access to registryCredentialTrustSecurityLOWRequires appropriate access controlsAcceptanceImplement Trust Registries
54
Inapproriate access writes to registryCredentialTrustData IntegrityLOWRequires appropriate access management controlsAcceptanceImplement Trust Registries
55
Breach of registryCredentialTrustSecurityLOWRequires appropriate security perimeter, breach detection and notification controlsAcceptanceImplement Trust Registries
56
Exploited Use of Stolen CredentialsCredentialTrustData IntegrityLOWRequires Adequate Breach Notifiaction ProcessesAcceptanceImplement Trust Registries
57
Credential Registry Not Accepted by Ecosystem EcosystemPersonal Self-DevelopmentGovernance42MEDIUMRequires Credential Verifier Conformance ProceduresAcceptanceImplement Trust Registries, added to the GF
58
Credential Registry Risks (Out of current Scope)
59
Lack of competence to perform roleCredentialTrustGovernanceLOWRequires training, trust assurance practices and controlled practicesAcceptance
60
Unavailable registryCredentialTrustAvailabilityLOWRequires availability controlsAcceptance
61
Lack of appropriate access to registryCredentialTrustSecurityLOWRequires appropriate access controlsAcceptance
62
Inapproriate access writes to registryCredentialTrustData IntegrityLOWRequires appropriate access management controlsAcceptance
63
Breach of registryCredentialTrustSecurityLOWRequires appropriate security perimeter, breach detection and notification controlsAcceptance
64
Exploited Use of Stolen CredentialsCredentialTrustData IntegrityLOWRequires Adequate Breach Notifiaction ProcessesAcceptance
65
Credential Registry Not Accepted by Ecosystem EcosystemTrustGovernanceLOWRequires Credential Verifier Conformance ProceduresAcceptance
66
Audit Accreditor Risks
67
Insufficient vetting of auditor populationEcosystemTrustGovernanceLOWRequires training, and generally accepted auditor accreditor practicesAcceptance
68
Lack of competence to perform roleEcosystemTrustGovernanceLOWRequires training, and generally accepted auditor accreditor practicesAcceptance
69
Auditor Risks
70
Lack of competence to perform roleEcosystemTrustGovernanceLOWRequires training, sufficient experience and generally accepted auditor practicesAcceptance
71
Credential Holder Risks (Yoma Members)
72
Holder Threat of Litigation over IssuerCredentialCommunityConfidentiality11LOWProper Agreement in pace between Issuer and Holder detailing rights.Acceptance
73
Counterfeit Credentials Being CreatedCredentialTrustData Integrity51LOW-MEDIUMRequires Adequate Credential Non-Repudiation PracticesAcceptance
74
Lack of Binding Between Holder and CredentialCredentialTrustData IntegrityLOWRequires Adequate Wallet Protection MeasuresAcceptance
75
Credential Holder Given Inappropriate Access RightsCredentialTrustSecurity51LOW-MEDIUMRequires Adequate User Enrolment ProcessesAcceptance
76
Imposter Using Valid CredentialCredentialTrustSecurity54HIGHRequires Adequate Wallet Protection MeasuresTransferenceConsider implementation of wallet compromise measures (e.g. private key rotation)
77
Credential Wallet Private Key is CompromisedCredentialTrustSecurity55HIGHRequires Adequate User Wallet Protection MeasuresTransferenceConsider implementation of wallet compromise measures (e.g. private key rotation)
78
Credential Holder's Private Data is CompromisedCredentialTrustPrivacy55HIGHRequires Adequate User Wallet Protection MeasuresTransferenceConsider implementation of wallet compromise measures (e.g. private key rotation)
79
Lack of Portability of CredentialCredentialPersonal Self-DevelopmentData Integrity53MEDIUM-HIGHRequires Adequate Credetial Interoperability PracticesTransferenceCredential Standards specified in GF Technical Requirements Controlled document
80
Lack of Credential Federation Across EcosystemsEcosystemCommunityGovernance43MEDIUMRequires Adequate Credetial Interoperability PracticesAvoidanceInteroperability rules for standards at layer 3 in GF
81
Exploited Private PIN Code CaptureCredentialPrivacyConfidentiality52MEDIUMRequires Adequate Wallet Protection MeasuresAcceptanceCurrently Cloud Wallet - always have a cloud wallet option with appropriate security controls
82
Social Engineering Attacks Sucessfully Gather Credentials by PerpetratorsCredentialPrivacySecurity52MEDIUMRequires Adequate Wallet Protection MeasuresAcceptanceCurrently Cloud Wallet - always have a cloud wallet option with appropriate security controls
83
Provider Risk
84
Provider Software Does not Operate as IntendedProviderTrustData Integrity22LOW-MEDIUMRequires Adequate Provider SDLC ProcessesAcceptanceRemove reliance on external TPs
85
Provider Software Does Not Operate on User DevicesProviderTrustData Integrity23LOW-MEDIUMRequires Adequate Provider SDLC ProcessesAcceptanceRemove reliance on external TPs
86
Provider Code Updates Cause Operational IssuesProviderTrustData Integrity43MEDIUMRequires Adequate Provider SDLC ProcessesAcceptanceRemove reliance on external TPs
87
Provider System UnavailableProviderTrustAvailability52MEDIUMRequires Adequate Provider Hardware Integration Practices AcceptanceRemove reliance on external TPs
88
Utility Risks
89
Inconsistent Steward Acceptance PracticesUtilityPrivacyGovernance32LOW-MEDIUMRequires Adequate Utliity Steward Aceptance PracticesAcceptanceCommunication & Alignment with Ulility Providers
90
Stewards Not Abiding by Governance PracticesUtilityTrustGovernance42MEDIUMRequires Adequate Steward Conformance PracticesAcceptanceCommunication & Alignment with Ulility Providers
91
Stewardship Not Available to Qualified ApplicantsUtilityFairnessGovernance24MEDIUMRequires Adequate Utliity Steward Aceptance PracticesAcceptanceCommunication & Alignment with Ulility Providers
92
Utility Not a Viable Going ConcernUtilityTrustGovernance51LOW-MEDIUMRequires Adequate Utility Monitoring PracticesAcceptanceCommunication & Alignment with Ulility Providers
93
Utility Using an Ineffective Consensus ModelUtilityTrustGovernance51LOW-MEDIUMRequires Adequate Utility Monitoring PracticesAcceptanceCommunication & Alignment with Ulility Providers
94
Utility Consensus Model Not Operating as Designed.UtilityTrustGovernance31LOWRequires Adequate Utility Monitoring PracticesAcceptanceCommunication & Alignment with Ulility Providers
95
Utility Charging Inaccurate Fees For ServiceUtilityFairnessGovernance32LOW-MEDIUMRequires Adequate Utility Monitoring PracticesAcceptanceCommunication & Alignment with Ulility Providers
96
Inadequate Number of Stewards for Consensus ProtocolUtilityTrustGovernance51LOW-MEDIUMRequires Adequate Utility Monitoring PracticesAcceptanceCommunication & Alignment with Ulility Providers
97
Inadequate Infrastructure Supporting Steward OperationsUtilityTrustAvailability41LOW-MEDIUMRequires Adequate Steward Conformance PracticesAcceptanceCommunication & Alignment with Ulility Providers
98
Inadequate Network Throughput Supporting Steward OperationsUtilityTrustAvailability21LOWRequires Adequate Steward Conformance PracticesAcceptanceCommunication & Alignment with Ulility Providers
99
Inadequate Network Availability Supporting Steward OperationsUtilityTrustAvailability31LOWRequires Adequate Steward Conformance PracticesAcceptanceCommunication & Alignment with Ulility Providers
100