The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Backtracking intrusions
Abstract
Analyzing intrusions today is an arduous, largely manual task because system administrators lack the information and tools needed to understand easily the sequence of steps that occurred in an attack. The goal of BackTracker is to identify automatically potential sequences of steps that occurred in an intrusion. Starting with a single detection point (e.g., a suspicious file), BackTracker identifies files and processes that could have affected that detection point and displays chains of events in a dependency graph. We use BackTracker to analyze several real attacks against computers that we set up as honeypots. In each case, BackTracker is able to highlight effectively the entry point used to gain access to the system and the sequence of steps from that entry point to the point at which we noticed the intrusion. The logging required to support BackTracker added 9% overhead in running time and generated 1.2 GB per day of log data for an operating-system intensive workload.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Time, clocks, and the ordering of events in a distributed system
Lamport, L. (1978) · Communications of the ACM · doi:10.1145/359545.359563 · Cited by 8,488
Cited by
Panorama: capturing system-wide information flow for malware detection and analysis
Yin, H., Song, D., Egele, M., Kruegel, C., & Kirda, E. (2007) · Proceedings of the 14th ACM conference on Computer and communications security · doi:10.1145/1315245.1315261 · Cited by 683
Zyzzyva: speculative byzantine fault tolerance
Kotla, R., Alvisi, L., Dahlin, M., Clement, A., & Wong, E. (2007) · Proceedings of twenty-first ACM SIGOPS symposium on Operating systems principles · doi:10.1145/1294261.1294267 · Cited by 638
NoDoze: Combatting Threat Alert Fatigue with Automated Provenance Triage
Hassan, W. U., Guo, S., Li, D., Chen, Z., Jee, K., Li, Z., & Bates, A. (2019) · Proceedings 2019 Network and Distributed System Security Symposium · doi:10.14722/ndss.2019.23349 · Cited by 341
Pioneer: verifying code integrity and enforcing untampered code execution on legacy systems
Seshadri, A., Luk, M., Shi, E., Perrig, A., van Doorn, L., & Khosla, P. (2005) · ACM SIGOPS Operating Systems Review · doi:10.1145/1095809.1095812 · Cited by 314
POIROT: Aligning Attack Behavior with Kernel Audit Records for Cyber Threat Hunting
Milajerdi, S. M., Eshete, B., Gjomemo, R., & Venkatakrishnan, V. N. (2019) · Proceedings of the 2019 ACM SIGSAC Conference on Computer and Communications Security · doi:10.1145/3319535.3363217 · Cited by 300
Metadata
- Authors
- King, S. T., & Chen, P. M.
- Venue
- Proceedings of the nineteenth ACM symposium on Operating systems principles
- Publisher
- ACM
- Published
- 2003-10-19
- Pages
- 223-236
- OpenAlex
- W4245671428
- Cited by
- 232
- References
- 1
- FWCI
- 3.08
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Backtracking intrusions. https://app.cochat.ai/papers/10.1145/945445.945467
- The paper
- King, S. T., & Chen, P. M. (2003). Backtracking intrusions. Proceedings of the nineteenth ACM symposium on Operating systems principles. https://doi.org/10.1145/945445.945467
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.