If the information collected is incorrectly provided, an organization needs to determine the level of accuracy that they require. Will you only use an exact match of what is provided or is “fuzzy matching” ok? For example, will you accept nicknames or is the full legal name required? Will you allow for minor typos, which could account for minor misspellings or being one numerical digit off on a date of birth or social security number? These are important items to consider when determining what is considered an “error”.
It is all related back to an organization’s compliance requirements and/or risk tolerances.
Remember that identity proofing is a multi-step process. We happen to group them into three steps — resolve, verify and authenticate. If information was given incorrectly, then this may limit our ability to resolve to a single identity and the identity proofing process would stop. If we are able to resolve to an identity and move to the next step of verification, most likely we wouldn’t be able to verify the data elements provided and the identity proofing process would stop. If we are able to verify the data elements provided, then authentication would give us the ability to leverage more data on file for that identity, where the subject shouldn’t be able to answer life history questions if the identity used was not his or hers.
