[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-19。"],[],[],null,["# Match likelihood\n\nScan results are categorized based on how likely they are to represent a match.\nSensitive Data Protection uses a bucketized\nrepresentation of likelihood, which is intended to indicate how likely it is\nthat a piece of data matches a given [infoType](/sensitive-data-protection/docs/infotypes-reference \"InfoTypes reference\").\n\nHow likelihood works\n--------------------\n\nWhen you configure a Sensitive Data Protection scan, you set the infoTypes\nthat you want Sensitive Data Protection to scan for. To narrow the scan\nresults, you can [set a *minimum likelihood level* in your\nrequest](#choose-min-likelihood).\n\nFor each potential match (*finding* ) that is detected during the scan,\nSensitive Data Protection assigns a likelihood level. The likelihood level of\na finding describes how likely it is that the finding matches an infoType that\nyou're scanning for. For example, Sensitive Data Protection might assign\na likelihood of `LIKELY` to a finding that looks like an email address.\n\nWhen Sensitive Data Protection returns the results, it filters out any\nfindings that have a lower likelihood than the minimum likelihood level that you\nset in your request. For example, if you set the minimum likelihood to\n`POSSIBLE`, you get only the findings that were evaluated as `POSSIBLE`,\n`LIKELY`, and `VERY_LIKELY`. If you set the minimum likelihood to `VERY_LIKELY`,\nyou get the smallest number of findings.\n| **Tip:** In your request, you can set the same minimum likelihood level for all infoTypes that you're scanning for. Alternatively, you can [set specific\n| minimum likelihood levels for specific\n| infoTypes](/sensitive-data-protection/docs/reference/rest/v2/InspectConfig#FIELDS.min_likelihood_per_info_type).\n\nLikelihood levels\n-----------------\n\nThe following table lists the possible likelihood values that\nSensitive Data Protection can assign to a finding.\n\nChoosing a minimum likelihood level for the scan results\n--------------------------------------------------------\n\nIn general, when you set a higher minimum likelihood level in your\nSensitive Data Protection request, the results have a lower number of false\npositives (sometimes called *noise* ). However, the results can also exclude more\ntrue positives. Choosing a minimum likelihood level involves finding the right\nbalance between [recall and\nprecision](https://en.wikipedia.org/wiki/Precision_and_recall).\n\nFor example, suppose that there are 10 street addresses in a document and\nSensitive Data Protection identified 5 street addresses. However,\namong the findings that Sensitive Data Protection identified, there are\nactually only 4 street addresses.\n\n- *Recall* is the number of true positive instances out of the total number of relevant instances. In this example, the recall is 4/10.\n- *Precision* is the number of true positive instances out of the total number of instances that Sensitive Data Protection identifies. In this example, the precision is 4/5.\n\nIn this example, the precision is high but the recall is relatively low.\n\nThe minimum likelihood level that you set affects the level of recall and\nprecision that you get in your scan results. The following table describes when\neach minimum likelihood level is useful and how recall and precision vary at\neach level.\n\nDefault minimum likelihood\n--------------------------\n\nIf you don't set a minimum likelihood in your request, or if you set it to\n`LIKELIHOOD_UNSPECIFIED`, Sensitive Data Protection returns only the findings with\na likelihood of `POSSIBLE` and higher."]]