참고 자료 · 29

보안 이벤트 로그를 탐지에 대비하도록 준비하세요.

이벤트를 선택하고, 기록을 보호하고, 시스템을 상호 연관시키고, 대응을 연습하세요.

업데이트됨 · 26 min

네트워크 수집 장비, 케이블, 추상 이벤트 화면과 버건디 파일이 있는 가상의 무인 사이버 수집실 AI로 생성한 편집용 일러스트

이 가이드가 달성하는 목표

  • 이벤트 정의
  • 기록 보호
  • 신호 상관관계 분석
  • 탐지 테스트

빠른 확인

  • 어떤 시스템이 중요한 여정을 지원하는가?
  • 시계와 식별자를 통해 타임라인을 재구성할 수 있는가?
  • 누가 기록을 읽거나 변경할 수 있는가?
  • 어떤 시나리오에서 경고가 발생하는가?
  • 다음 조치를 알고 있는 사람이 있는가?

단계별 방법

  1. 1

    소스 선택

    서비스 및 위협 시나리오(로그인, 권한 변경, 데이터 액세스, API, 네트워크 및 인프라)에서 시작합니다. 필요한 이벤트와 담당자를 정의합니다.

    결과물: 소스 수준 로깅 정책

  2. 2

    컨텍스트 정규화

    시계, 시간대, 요청 식별자, 행위자, 결과 및 발신 시스템을 명시합니다. 불필요한 비밀 정보와 개인 데이터는 메시지에서 제외합니다.

    결과물: 이벤트 스키마 및 최소화 규칙.

  3. 3

    중앙 집중화 및 보호

    전송, 가용성, 권한, 보존 및 변조 탐지를 테스트합니다. 손상된 시스템은 유일하게 유용한 증거를 조용히 삭제해서는 안 됩니다.

    결과물: 전송 및 무결성 검사.

  4. 4

    시나리오 상관관계 분석

    의심스러운 로그인 후 API 호출 또는 민감한 변경이 발생하는 시나리오를 시뮬레이션합니다. 이벤트가 시간과 식별자를 기준으로 일치하는지 확인합니다.

    결과물: 재구성된 타임라인 및 격차 목록.

  5. 5

    탐지 최적화

    조건, 임계값, 예외, 소유자 및 우선순위를 포함하는 규칙을 작성합니다. 승인된 시나리오를 사용하여 오탐 및 누락된 이벤트를 측정합니다.

    결과물: 테스트된 규칙 및 유효성 검사 사례.

  6. 6

    대응 연습

    담당자에게 경고를 전달하고, 조사를 시작하고, 증거를 보존하고, 종결 여부를 확인합니다. 연습 후 스키마 또는 규칙을 개선합니다.

    결과물: 날짜가 기재된 연습 및 후속 조치.

이해하고 계산하고 판단하기

로그: 이벤트 시각과 수신 시각 구분하기

로그 수신은 탐지나 경고 처리 완료를 뜻하지 않습니다. 이 가상 사례는 같은 계정의 로그인 실패 두 번과 성공 한 번을 추적합니다. 시각은 공통 시작점부터의 초 단위이며 시계 동기화를 가정합니다.

이벤트 시각과 수신 시각을 따로 보관하세요. 누락, 지연, 읽기 권한, 대응 담당자를 시험합니다. 암호, 접근 토큰, 전체 요청 본문을 로그에 기록하지 마세요.

관찰된 행동 → 수집된 이벤트 → 생성된 경고 → 검증된 대응
로그에서 검증된 탐지까지 — 허가된 훈련에서 시험 로그인은 로그를 만들었지만 경고는 발생하지 않았습니다. 수집은 작동하지만 탐지는 입증되지 않았습니다. ATT&CK 기술을 대응 완료로 표시하기 전에 전체 연결을 확인하세요. MITRE ATT&CK

지표와 근거

지표해석필요한 근거
E1 0초에 실패, 2초에 수신 지연: 2초
E2 20초에 실패, 140초에 수신 지연: 120초
E3 35초에 성공, 36초에 수신 지연: 1초

로그별 지연 보기

이벤트 시각 기준으로 E1, E2, E3은 1분 안에 있습니다. 수신 시각으로는 E2가 늦게, 성공 이후에 도착합니다. 지연 이벤트 정책과 담당자에게 경고가 전달되는지 시험하세요. 교육용 규칙만으로 공격을 입증할 수는 없습니다.

로그별 지연 보기

공통 눈금은 0~150초입니다. 밝은 원은 이벤트, 금색 사각형은 수신, 선분은 지연입니다. 표에도 같은 값이 있습니다.

  • E10 s → 2 s (+2 s)
  • E220 s → 140 s (+120 s)
  • E335 s → 36 s (+1 s)

관리 지표

지표측정 대상첫 번째 조치
범위예상 이벤트가 있는 중요 소스누락된 소스 추가
지연조치부터 검색 가능한 기록까지의 시간전송 복구
상관관계 분석시나리오를 처음부터 끝까지 재구성컨텍스트 또는 식별자 추가
대응담당자 및 조치가 포함된 테스트된 알림규칙 또는 온콜 경로 수정

일반적인 실수

  • 시나리오 우선순위 지정 없이 모든 데이터 수집
  • 비밀 정보 또는 민감한 데이터를 평문으로 로깅
  • 무결성 및 권한 검사 없이 중앙 집중화
  • 처리 절차 없이 알림 추가

자주 묻는 질문

로그가 많을수록 탐지율이 높아지는가?

아닙니다. 로그의 양뿐만 아니라 품질, 컨텍스트 및 대응 능력도 중요합니다.

왜 시간 동기화가 필요한가?

일관되지 않은 타임라인은 상관관계 분석 및 사고 대응 결정의 신뢰성을 떨어뜨립니다.

규칙 준비 완료 시점은 언제인가요?

승인된 시나리오에서 예상되는 신호가 발생하고 담당자가 문제를 분류할 수 있을 때입니다.

참고 자료: 데이터, 용도와 한계

문서 검토일 .

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

참고 자료: 데이터, 용도와 한계
출처와 목적확인된 데이터 또는 기준사용 방법유지해야 할 한계
OASIS · STIX 2.1

Describe threat intelligence through structured objects and relationships.

STIX 2.1 is an OASIS Standard dated 10 June 2021. It defines objects, properties and JSON serialisation. Keep identifiers, dates, provenance and relationships. Check that the recipient interprets the same object type and validity period.

방법 자세히 보기 →

A syntactically valid object can still be stale, misattributed or weakly supported.
MITRE ATT&CK

Connect observations with adversary tactics and techniques.

ATT&CK is a knowledge base grounded in observations. Its domains include Enterprise, Mobile and ICS. Connect a technique with a trace and detection hypothesis. Distinguish having a log source from actually testing detection.

방법 자세히 보기 →

A shared technique cannot establish actor attribution. Technique coverage counts do not fully measure security.

STIX 지표와 TLP 공유

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

Cyber threat intelligence: from an indicator to a defensible detection

A threat intelligence feed may deliver a domain, a detection pattern and a confidence assessment. A SOC still needs its provenance, useful time window, telemetry capable of recognising it and a retirement procedure. This reference helps prepare that decision and explain its limits to the recipient.

The properties and objects described here refer to the OASIS STIX 2.1 Standard dated 10 June 2021. Deployment checks, review deadlines and case decisions are local editorial proposals. This page is neither a STIX validator, a blocking rule nor an assessment of a real feed.

Version note: at review time the OASIS latest-stage URL points to a document dated 2 April 2025 titled STIX 2.1 Errata 01, incorporating Draft 01. Its draft errata status is retained in the citation; it is not presented as a newly approved final version. Agree marking encodings with the recipient and check the edition actually used.

Local indicator lifecycle and a separate sharing check
Local indicator lifecycle and a separate sharing check Four steps: preserve source and version; qualify validity and context; test detection against logs; review and propagate retirement. TLP scope is checked at every disclosure, independently of confidence. 1 · Preserve Source and version Receipt time 2 · Qualify Validity and context Explicit confidence 3 · Test Logs and coverage Exceptions and decision 4 · Review Review deadline Retirement propagated At every disclosure: check TLP, recipients and source restrictions.

Four steps: preserve source and version; qualify validity and context; test detection against logs; review and propagate retirement. TLP scope is checked at every disclosure, independently of confidence.

12 reading checks before importing an indicator

12 reading checks before importing an indicator
STIX 2.1 propertyWhat it tells youOperational check to record
id / modifiedA versioned object retains its id; modified identifies its version.Compare received versions before overwriting local state. A later delivery can contain an older version.
created_by_refOptional reference to the creator’s Identity; when absent, this property leaves the source undefined.Also preserve collection provenance. A TAXII relay is not necessarily the intelligence creator.
created / modifiedObject creation and version modification times; modified is at least equal to created.Do not treat them as first and last observed activity times.
pattern / pattern_typeBoth the pattern and its language are required; a STIX pattern describes a condition to recognise.Check language, version, parser and available telemetry fields before translating it into a SIEM rule.
valid_fromRequired start of the Indicator’s validity window.A future start calls for holding or review; it does not establish current activity.
valid_untilOptional end, strictly later than valid_from when present. At this time the indicator should no longer be considered valid.Without an end the standard sets no upper time bound. Still assign a local review date without inventing a producer expiry.
revokedPermanent withdrawal by the creator. No future version of the same id may be created after revocation.Propagate withdrawal to derived uses and preserve the record. Expiry or a local false positive does not automatically mean revoked=true.
confidenceOptional integer from 0 to 100 expressing the creator’s confidence in data correctness; absence means unspecified.Preserve the producer’s method. Do not turn 60 into a 60% probability of compromise, or absence into zero.
external_referencesLinks, descriptions or identifiers referring to external information.Check origin and access to cited evidence. Multiple copies of one report are not independent sources.
object_marking_refsReferences to marking-definition objects applying to the object.Resolve references and preserve restrictions in copies, tickets and summaries.
granular_markingsMarkings or languages applying to specific parts of an object.Check the relevant fields before quoting an excerpt; a title’s marking does not establish the pattern’s marking.
description / indicator_typesNarrative context and categories help interpretation; these properties are optional.Explain the behaviour sought, prerequisites, possible legitimate uses and person responsible for review.

Four objects answering four different questions

Four objects answering four different questions
ObjectQuestion it answersAnalytical limit
IndicatorWhat pattern could recognise suspicious activity?A usable pattern is not evidence that the activity occurred in your environment.
Observed DataWhat data was observed, and during which window?Observed facts alone do not establish attribution or malicious intent.
SightingWhich intelligence entity does the reporter believe they saw?The assertion may reference Observed Data. Sighting count and number_observed measure different things.
RelationshipWhat link is asserted between two objects?An indicates or based-on link has a specific meaning. A dense graph does not prove attribution.

Read a fictional object without turning it into an alert

A standalone training example written for this page; no real threat intelligence. RFC 2606 reserves .example for documentation. Dates and confidence 60 are fictional. Creator and marking are deliberately absent: this establishes neither a verified source nor permission to publish. This is neither a complete bundle nor an OASIS-tool compliance validation.

{
    "type": "indicator",
    "spec_version": "2.1",
    "id": "indicator--643d2844-11ca-4f63-8d5d-e5d938db1854",
    "created": "2026-10-22T09:00:00.000Z",
    "modified": "2026-10-22T09:00:00.000Z",
    "lang": "en",
    "name": "Fictional training indicator",
    "description": "Documentation only. Never deploy this example as a detection or blocking rule.",
    "pattern": "[domain-name:value = 'training-beacon.example']",
    "pattern_type": "stix",
    "pattern_version": "2.1",
    "valid_from": "2026-10-22T09:00:00Z",
    "valid_until": "2026-10-23T09:00:00Z",
    "confidence": 60
}

At 10:00 UTC on 22 October 2026, the time falls inside the stated window. This establishes neither a log match nor maliciousness. Deriving a detection would still require the producer, context, restrictions, telemetry, exceptions and retirement owner.

Eight fictional qualification and sharing cases

Each case isolates one difficulty. Suggested decisions belong to a local working method, rather than automatic verdicts from STIX syntax alone. The filter only hides examples already in the page; it sends no data.

Validity starts tomorrow

The pattern arrives today; valid_from is tomorrow.

Retain the object for review and schedule assessment at the appropriate time; receipt alone does not justify immediate blocking.

Keep receipt time, evaluation time and object version. Historical investigation has a different purpose.

Validity end reached

At 09:00 UTC, valid_until is reached; a derived rule remains active.

Remove the object from active candidates or trigger the planned retirement process, then check derived rules.

Retain history and the withdrawal rationale. The deadline does not prove past events were benign.

Revocation received after import

A new version of the same id contains revoked=true.

Propagate withdrawal to dependent uses and verify each consumer’s state.

Keep the received version and propagation record; do not reactivate the object from an older copy.

Confidence unspecified

The feed provides no confidence; an interface proposes displaying 0.

Display unspecified, request provenance and describe available corroboration.

An internal scoring convention may exist, but must be named and kept separate from the producer’s value.

Shared domain and DNS log

A cited domain appears in a DNS log; it also hosts legitimate uses.

Inspect the exact name, time, host and related events; prepare a focused search before broad action.

DNS resolution demonstrates neither download, execution nor compromise. Plan exceptions and rollback.

Sighting count=0

A producer publishes a Sighting with count=0.

Read this as a non-observation statement in its context, then ask about window and coverage.

Zero does not measure worldwide absence of the threat. It does not replace checks of your own sensors.

Client and AMBER+STRICT

A recipient wants to forward a TLP:AMBER+STRICT note to a client.

The restriction limits sharing to the organisation on a need-to-know basis; obtain explicit source permission to widen it.

Do not mistakenly apply the client-sharing scope associated with AMBER without STRICT.

GREEN message to a public channel

A TLP:GREEN note is proposed for a public article.

Keep the note inside the permitted community; ask the source for permission to share more widely.

A publicly accessible web page exceeds GREEN’s scope. Source attribution does not lift the restriction.

TLP 2.0: recipients, need to know and restrictions

FIRST defines four labels; AMBER+STRICT restricts AMBER rather than adding a fifth colour. Labels remain unchanged across languages. This matrix summarises TLP scope and does not replace additional source restrictions or applicable document rules.

TLP 2.0: recipients, need to know and restrictions
MarkingSharing scopeCheck
TLP:REDIndividual recipients only; no further disclosure.A colleague’s membership of the same organisation does not authorise forwarding.
TLP:AMBEROrganisation and clients on a need-to-know basis to protect them and prevent further harm.Check that the recipient needs the information and no additional restriction narrows this scope.
TLP:AMBER+STRICTOrganisation only, on a need-to-know basis.Clients are not included by default under this restriction.
TLP:GREENThe relevant community; no publicly accessible channels.When the community is undefined, FIRST assumes the cybersecurity/defence community.
TLP:CLEARNo TLP disclosure limit, subject in particular to copyright rules.Preserve origin, separate restrictions and applicable public-release procedures.

TLP describes a sharing scope; it certifies neither accuracy, official classification nor a usage licence. Encryption and retention rules need separate definition. Obtain explicit source permission before widening the received scope.

Interoperability check: predefined TLP markings in the 2021 STIX 2.1 edition include TLP:WHITE. FIRST’s TLP 2.0 vocabulary uses TLP:CLEAR and specifies AMBER+STRICT. Do not invent a tlp=clear encoding or silently rename historical markings: document the version and exchange profile actually supported by the tools.

Six elements to hand over with the decision

  • Object identifier and version, declared producer and collection provenance.
  • UTC timestamps: receipt, validity window and a clearly separate local review date.
  • Detection hypothesis, required logs, fields used and known sensor coverage.
  • Search results and limits: absence, match, ambiguity or a justified false positive.
  • Recipients, markings, additional restrictions and permission to widen scope where applicable.
  • Owner, derived rule or ticket, decision, planned retirement and propagation verification.

References and verification scope

Sources checked on

syslog 코드와 수집 증거

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

Syslog priority combines a message family (facility) and a declared severity. It helps interpret a log stream but measures neither attack likelihood nor business incident urgency. Check what the sender encodes and what the collector preserves.

32 official values: 24 facilities and 8 severities. IANA registry updated 26 April 2016, consulted 23 October 2026. Cases and acceptance questions below are original CIE editorial examples.

IANA · syslog Parameters · Registry updated 2016-04-26 · consulted 2026-10-23

How do you calculate and decode syslog priority?

PRI = facility × 8 + severity. Reverse it with facility = integer quotient of PRI / 8 and severity = remainder of PRI / 8. The 192 combinations span 0–191. The field uses angle brackets and no leading zero except <0>. Example: 20 × 8 + 5 = 165, written <165>.

PRI is not a global danger ranking: <184> combines local7 and Emergency while <7> combines kernel and Debug. Interpret severity in the source context. A declared value or hostname does not authenticate a message.

IETF · R. Gerhards · RFC 5424 · The Syslog Protocol · March 2009 · §6.2.1 PRI · §6 format · §8 security

PRI 계산

Choose two codes or enter only a PRI integer, with or without angle brackets. Accepted examples: 0, 165, <165>, <191>. Spaces, signs, decimals, leading zeros and complete messages are rejected. Calculation stays on this page; it does not connect to your equipment.

Official facility and severity tables

The registry’s English labels are preserved. A local0–local7 code does not identify the product or service that emitted it: your organisation must document its operational meaning.

24 facilities · codes 0–23

24 facilities · codes 0–23
CodeOfficial IANA labelRegistry note
0kernel messages
1user-level messages
2mail system
3system daemons
4security/authorization messagesCodes 4, 10, 13 and 14 have similar security, authorization, audit and alert uses across operating systems.
5messages generated internally by syslogd
6line printer subsystem
7network news subsystem
8UUCP subsystem
9clock daemonBoth codes 9 and 15 are used for clock or scheduled-job messages across operating systems.
10security/authorization messagesCodes 4, 10, 13 and 14 have similar security, authorization, audit and alert uses across operating systems.
11FTP daemon
12NTP subsystem
13log auditCodes 4, 10, 13 and 14 have similar security, authorization, audit and alert uses across operating systems.
14log alertCodes 4, 10, 13 and 14 have similar security, authorization, audit and alert uses across operating systems.
15clock daemonBoth codes 9 and 15 are used for clock or scheduled-job messages across operating systems.
16local use 0 (local0)
17local use 1 (local1)
18local use 2 (local2)
19local use 3 (local3)
20local use 4 (local4)
21local use 5 (local5)
22local use 6 (local6)
23local use 7 (local7)

8 severities · codes 0–7

8 severities · codes 0–7
CodeOfficial IANA labelRegistry note
0Emergency: system is unusable
1Alert: action must be taken immediately
2Critical: critical conditions
3Error: error conditions
4Warning: warning conditions
5Notice: normal but significant condition
6Informational: informational messages
7Debug: debug-level messages

IANA · Licensing Terms · Protocol Registries CC0 1.0 · Revised 2021-11-10 · original CIE commentary identified separately

Read a message before building a rule

Fictional example, containing no production data:

<165>1 2026-10-23T09:14:00Z gateway.example.net app 742 EVT42 [meta sequenceId="12"] Cache refreshed
Read a message before building a rule
ElementReading this exampleAcceptance consideration
<165>facility 20, severity 5Document the sender’s convention.
1Format versionDistinguish the received format from collector-added labels.
TIMESTAMPSource timestamp in UTCCheck reception time and clock drift as well.
HOSTNAME / APP-NAMEgateway.example.net / appConnect the declaration to your equipment inventory.
PROCID / MSGID742 / EVT42Do not treat a process number as a universal identifier.
STRUCTURED-DATAmeta with sequenceId 12Preserve names and parameters without flattening distinct identifiers.
MSGCache refreshedDo not log secrets to enrich an event.

A NILVALUE hyphen marks unavailable information in fields that allow it; it does not mean zero. Decoding PRI alone validates neither the rest of a message, its timestamp nor its transport.

Eight explained calculations · fictional situations

Eight explained calculations · fictional situations
Facility / severityCalculation and PRIInterpretation and limit
0 / 00 × 8 + 0 = 0 · <0>Kernel / Emergency: encoding an outage does not establish its cause.
1 / 51 × 8 + 5 = 13 · <13>User-level / Notice: a notable condition may still be normal.
4 / 24 × 8 + 2 = 34 · <34>Security / Critical: qualify the rule and asset before escalating.
10 / 510 × 8 + 5 = 85 · <85>Security / Notice: one family can carry a different severity.
13 / 613 × 8 + 6 = 110 · <110>Audit / Informational: an informative event can be decisive in an investigation.
20 / 520 × 8 + 5 = 165 · <165>Local4 / Notice: document the local convention; no universal product meaning.
23 / 023 × 8 + 0 = 184 · <184>Local7 / Emergency: high PRI, most severe level on this severity scale.
23 / 723 × 8 + 7 = 191 · <191>Local7 / Debug: same facility, eighth level, not evidence of harmlessness.

Collection acceptance: what evidence should you request?

Correct decoding does not establish useful detection. The joint guidance published by ASD ACSC and partners in 2024 addresses policy, centralisation, protected storage and detection strategy. This CIE acceptance proposal should be adapted to the service.

Collection acceptance: what evidence should you request?
CIE checkPractical exerciseExpected evidence
Source coverageTrigger an identified test event on a critical source.Find source, collector, index and owner; record absent sources.
Severity conventionCompare a known event before and after normalisation.Preserve raw code, normalised value and versioned conversion rule.
Identity and correlationFollow a fictional sign-in and subsequent application action.Connect useful identifiers without logging tokens, passwords or sensitive content.
Time and delayCompare source time, reception and search availability.Separate clock drift, transport delay and indexing delay.
Loss and recoveryInterrupt an authorised test stream and restore it.Observe gaps, queues, possible duplicates and missing-stream alerts.
Truncation and parsingFeed a long message and malformed event into the test pipeline.Record received size, lost fields or rejection; do not equate rejection with inactivity.
Path protectionReview transfer, access and retention with the owners.Identify every hop, permissions and the protection mechanisms actually configured.
Detection and responseTrigger a rule in an authorised scenario and follow handling.Connect event, alert, qualification, decision and observed result.

ASD ACSC and partners · Best practices for event logging and threat detection · Published and reviewed 2024-08-22 · consulted 2026-10-23

Set retention, scope and thresholds according to investigation needs and the service’s applicable constraints. This table defines neither a universal retention period nor SIEM certification. A format check cannot replace an end-to-end exercise.

Value provenance and consulted edition

IANA · 32 codes · registry 2016-04-26 · reviewed 2026-10-23 · CC0 1.0

IANA XML SHA-256: 10eb91ad6e29dc6fdebe5320cc0b2711ce840c1ed7a6d2c33c4bc716423b4ec6

RFC 5424 TXT SHA-256: 24d91f90a05d2536730ada929c296f45ae9cd72226e22b6775ad8c04cae37a53

Commentary, cases and acceptance proposal: Cyber Intelligence Embassy. IANA labels are reproduced for reference.

공식 참조

참조는 방법을 뒷받침합니다. 상황에 맞게 검사를 조정하십시오. 이는 인증이 아닙니다. 원본 참조 제목 및 소스 문서는 다른 언어로 작성되었을 수 있습니다.

참고 자료 확인일 .