이제 Cloud Data Loss Prevention(Cloud DLP)은 민감한 정보 보호에 포함됩니다. API 이름은 Cloud Data Loss Prevention API(DLP API)로 그대로 유지됩니다. 민감한 정보 보호를 구성하는 서비스에 대한 자세한 내용은 민감한 정보 보호 개요를 참조하세요.
스캔 범위를 선택하라는 메시지가 표시되면 단일 리소스 옵션을 선택한 다음 리소스의 세부정보를 입력합니다.
프로필 재생성
Sensitive Data Protection은 데이터 프로필 생성 빈도에 설명된 대로 데이터를 다시 프로파일링합니다. 일정을 만들어 스캔 구성에서 프로파일링 빈도를 맞춤설정할 수 있습니다.
디스커버리 서비스에서 데이터를 다시 프로파일링하도록 강제하려면 다시 프로파일링 작업 강제 실행을 참고하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],null,["# Profile a single data resource\n\nIf you only want to profile a single data resource, you can do so by creating a project-level scan configuration.\n\n\u003cbr /\u003e\n\nSupported resources\n-------------------\n\nThe following resource types are supported:\n\n- BigQuery table\n- Cloud SQL table\n- Cloud Storage bucket\n- Vertex AI dataset\n- Amazon S3 bucket\n- Azure Blob Storage container\n\nDifferences between profiling a single data resource and standard profiling\n---------------------------------------------------------------------------\n\nSingle-resource profiling differs from standard profiling in the following ways:\n\n- Single-resource profiling is available only in project view.\n- A single-resource discovery configuration lets you profile only one data resource. You can't add schedules to the configuration, but you can edit the catch-all schedule. You can't add filters to the schedule.\n- You can create many single-resource discovery configurations for different data resources in a project. For each data resource, you can have only one single-resource discovery configuration.\n\nCreate a single-resource discovery configuration\n------------------------------------------------\n\nTo create a single-resource discovery configuration, see the instructions for\nthe data that you want to profile:\n\n- [Profile BigQuery data in a single\n project](/sensitive-data-protection/docs/profile-project)\n- [Profile Cloud SQL data in a single\n project](/sensitive-data-protection/docs/profile-project-cloud-sql)\n- [Profile Cloud Storage data in a single\n project](/sensitive-data-protection/docs/profile-project-cloud-storage)\n- [Profile Vertex AI data in a single\n project](/sensitive-data-protection/docs/profile-project-vertex-ai)\n- [Discovery for Amazon S3\n data](/sensitive-data-protection/docs/profile-amazon-s3)\n\nWhen you're prompted to select the scope of the scan, select the single-resource\noption, and then enter the details of the resource.\n\nProfile regeneration\n--------------------\n\n\nSensitive Data Protection reprofiles data as described in [Frequency of data profile\ngeneration](/sensitive-data-protection/docs/data-profiles#scan-frequency). You can customize the profiling frequency in your scan configuration by [creating a schedule](/sensitive-data-protection/docs/profile-org-folder#manage-schedules).\nTo force the discovery service to reprofile your data, see [Force a reprofile\noperation](/sensitive-data-protection/docs/manage-data-profiles#force-reprofile)."]]
