{"id":"T1583.004","name":"Server","url":"https://attack.mitre.org/techniques/T1583/004","tactics":["resource-development"],"platforms":["PRE"],"live":true,"revoked":false,"deprecated":false,"revoked_by":null,"detection_strategies":[{"id":"DET0871","stix_id":"x-mitre-detection-strategy--c377533f-702a-4e82-a254-9855b9362c22","name":"Detection of Server","url":"https://attack.mitre.org/detectionstrategies/DET0871","analytics":[{"id":"AN2003","stix_id":"x-mitre-analytic--8ad0cc97-4f6e-4ea0-a930-3fdb6b0df819","name":"Analytic 2003","description":"Much of this activity will take place outside the visibility of the target organization, making detection of this behavior difficult. Detection efforts may be focused on related stages of the adversary lifecycle, such as during Command and Control.\nOnce adversaries have provisioned a server (ex: for use as a command and control server), internet scans may reveal servers that adversaries have acquired. Consider looking for identifiable patterns such as services listening, certificates in use, SSL/TLS negotiation features, or other response artifacts associated with adversary C2 software.(Citation: ThreatConnect Infrastructure Dec 2020)(Citation: Mandiant SCANdalous Jul 2020)(Citation: Koczwara Beacon Hunting Sep 2021)","url":"https://attack.mitre.org/detectionstrategies/DET0871#AN2003","platforms":["PRE"],"log_source_references":[{"name":"Internet Scan","channel":"None","data_component":"DC0106","data_component_name":"Response Metadata","log_source_slug":"internet-scan"},{"name":"Internet Scan","channel":"None","data_component":"DC0104","data_component_name":"Response Content","log_source_slug":"internet-scan"}],"mutable_elements":[],"live":true,"detection_strategies":["DET0871"],"techniques":["T1583.004"]}],"live":true,"version":"1.0","techniques":["T1583.004"]}],"sigma_rules":[],"kev_cves":[],"_built":"2026-08-23 05:47 UTC","_attack_version":"19.2","_sigma_commit":"da9bb07d642a2826e89702445d32c795209ec108"}