[[["이해하기 쉬움","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-09(UTC)"],[],[],null,["| Premium and Enterprise [service tiers](/security-command-center/docs/service-tiers)\n\nThis document describes a threat finding type in Security Command Center. Threat findings are generated by\n[threat detectors](/security-command-center/docs/concepts-security-sources#threats) when they detect\na potential threat in your cloud resources. For a full list of available threat findings, see [Threat findings index](/security-command-center/docs/threat-findings-index).\n\nOverview\n\nThe `startup-script` or `startup-script-url` Compute Engine instance metadata key\nwas changed on an instance that was created more than seven days ago.\n\nHow to respond\n\n\nThe following response plan might be appropriate for this finding, but might also impact operations.\nCarefully evaluate the information you gather in your investigation to determine the best way to\nresolve findings.\n\nTo respond to this finding, do the following:\n\n1. Verify whether the change was done intentionally by a member, or if it was\n implemented by an adversary to introduce new access to your organization.\n\n2. Check logs using the following filters:\n\n ```\n protopayload.resource.labels.instance_id=INSTANCE_ID\n protoPayload.serviceName=\"compute.googleapis.com\"\n ((protoPayload.metadata.instanceMetaData.addedMetadataKey : \"startup-script\" OR\n protoPayload.metadata.instanceMetaData.modifiedMetadataKey : \"startup-script\" ) OR\n (protoPayload.metadata.instanceMetaData.addedMetadataKey : \"startup-script-url\" OR\n protoPayload.metadata.instanceMetaData.modifiedMetadataKey : \"startup-script-url\" ))\n logName=\"organizations/ORGANIZATION_ID/logs/cloudaudit.googleapis.com%2Factivity\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e: the `gceInstanceId` listed in the finding\n - \u003cvar translate=\"no\"\u003eORGANIZATION_ID\u003c/var\u003e: your organization ID\n3. Research events that trigger this finding:\n\n - **MITRE:** \u003chttps://attack.mitre.org/techniques/T1098/004/\u003e\n\nWhat's next\n\n- Learn [how to work with threat\n findings in Security Command Center](/security-command-center/docs/how-to-investigate-threats).\n- Refer to the [Threat findings index](/security-command-center/docs/threat-findings-index).\n- Learn how to [review a\n finding](/security-command-center/docs/how-to-investigate-threats#reviewing_findings) through the Google Cloud console.\n- Learn about the [services that\n generate threat findings](/security-command-center/docs/concepts-security-sources#threats)."]]
