Lesson:moat securely mitigating rowhammer with per row activation counters 6e5ed0e1
| 제목 | MOAT: Securely Mitigating Rowhammer with Per-Row Activation Counters |
|---|---|
| 궁금했던 점 | Can DDR5 per-row activation counting and ALERT back-off be implemented with provable RowHammer security and low overhead? |
| 해본 것 | MOAT uses an eligibility threshold for proactive mitigation, an ALERT threshold for ABO, highest-count row tracking, and safe counter reset around refresh. |
| 당시 조건 | Venue: ASPLOS. Year: 2025.
PRAC+ABO specifies mechanisms, not a secure policy; Panopticon's queue can be manipulated by crafted activation patterns. Verification: full_text; confidence=high. |
| 실제 결과 | workloads=SPEC CPU; GAP graph workloads; Jailbreak and performance attacks; baselines=Panopticon; PRAC+ABO configurations; metrics=maximum aggressor activations; safe TRH; slowdown; SRAM overhead; results=Panopticon reaches 1,150 activations at threshold 128; MOAT ATH=64 safe for TRH=99; 0.28% average slowdown; 7 bytes SRAM per bank |
| 왜 그랬는지 | Accurate per-row counters are insufficient unless queue service, delayed alerts, and reset semantics are included in the security proof. |
| 다음에 기억할 것 | Prove the complete mitigation state machine against adversarial scheduling, including backpressure and counter reset. |
| 언제 맞는지 | DDR5 PRAC/ABO RowHammer mitigation designs.
Limits: Security bound depends on timing and threshold assumptions; evaluation is simulation/workload based and must track JEDEC/device implementation details. |
| 신뢰도 | 높음 |
| 관련 자료 | MOAT: Securely Mitigating Rowhammer with Per-Row Activation Counters. ASPLOS 2025. |
| 자료 출처 | 우리 기록 |
| 작성자 | S3ResearchAgent |
| 처음 작성한 시각 (UTC) | 2026-07-16T14:58:25.155284Z |
| 마지막 수정 시각 (UTC) | 2026-07-18T14:58:45.195938Z |
근거 ev_6fbdb1b582084fad: MOAT: Securely Mitigating Rowhammer with Per-Row Activation Counters. ASPLOS 2025.
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T14:58:26.086142Z
Bibliographic paper record.
근거 verified-content-v1-0106: Moinuddin Qureshi et al., "MOAT: Securely Mitigating Rowhammer with Per-Row Activation Counters", ASPLOS 2025.
(원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T18:55:56.912757Z
Verification: full_text; confidence=high.
Canonical title: MOAT: Securely Mitigating Rowhammer with Per-Row Activation Counters
Question: Can DDR5 per-row activation counting and ALERT back-off be implemented with provable RowHammer security and low overhead?
Context: PRAC+ABO specifies mechanisms, not a secure policy; Panopticon's queue can be manipulated by crafted activation patterns.
Method: MOAT uses an eligibility threshold for proactive mitigation, an ALERT threshold for ABO, highest-count row tracking, and safe counter reset around refresh.
Evaluation: workloads=SPEC CPU; GAP graph workloads; Jailbreak and performance attacks; baselines=Panopticon; PRAC+ABO configurations; metrics=maximum aggressor activations; safe TRH; slowdown; SRAM overhead; results=Panopticon reaches 1,150 activations at threshold 128; MOAT ATH=64 safe for TRH=99; 0.28% average slowdown; 7 bytes SRAM per bank
Interpretation: Accurate per-row counters are insufficient unless queue service, delayed alerts, and reset semantics are included in the security proof.
Reusable lesson: Prove the complete mitigation state machine against adversarial scheduling, including backpressure and counter reset.
Applicability: DDR5 PRAC/ABO RowHammer mitigation designs.
Limits: Security bound depends on timing and threshold assumptions; evaluation is simulation/workload based and must track JEDEC/device implementation details.
근거 canonical-paper-v2-6e5ed0e1: Moinuddin Qureshi et al., "MOAT: Securely Mitigating Rowhammer with Per-Row Activation Counters", ASPLOS 2025.
(원문 열기)
논문 · 확인 범위: 원문 확인 · S3ResearchAgent · 2026-07-18T05:30:01.276242Z
Verification: full_text; confidence=high.
Canonical title: MOAT: Securely Mitigating Rowhammer with Per-Row Activation Counters
Question: Can DDR5 per-row activation counting and ALERT back-off be implemented with provable RowHammer security and low overhead?
Context: PRAC+ABO specifies mechanisms, not a secure policy; Panopticon's queue can be manipulated by crafted activation patterns.
Method: MOAT uses an eligibility threshold for proactive mitigation, an ALERT threshold for ABO, highest-count row tracking, and safe counter reset around refresh.
Evaluation: workloads=SPEC CPU; GAP graph workloads; Jailbreak and performance attacks; baselines=Panopticon; PRAC+ABO configurations; metrics=maximum aggressor activations; safe TRH; slowdown; SRAM overhead; results=Panopticon reaches 1,150 activations at threshold 128; MOAT ATH=64 safe for TRH=99; 0.28% average slowdown; 7 bytes SRAM per bank
Interpretation: Accurate per-row counters are insufficient unless queue service, delayed alerts, and reset semantics are included in the security proof.
Reusable lesson: Prove the complete mitigation state machine against adversarial scheduling, including backpressure and counter reset.
Applicability: DDR5 PRAC/ABO RowHammer mitigation designs.
Limits: Security bound depends on timing and threshold assumptions; evaluation is simulation/workload based and must track JEDEC/device implementation details.
자료 검증 verify_8b67e36160d035629073:
ev_6fbdb1b582084fad ·
판단 보류
확인 범위: 서지정보만 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:44.974165Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9 / 위치: 보존 파일 objects/sha256/49/49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9
보존 객체는 cookie/landing page이므로 서지 위치만 확인했고 본문 주장을 검증하지 못함.
자료 검증 verify_ca977fe1bbd51e0083f9:
verified-content-v1-0106 ·
판단 보류
확인 범위: 서지정보만 확인 · 주장: context · S3ResearchAgent · 2026-07-18T14:58:45.195938Z
자료: R2-RESTIC:7f893ca5afd2cfb6fe320e9b61063ccc70e75a7a96589420038c8cf338b273be; archive-manifest-sha256=e28171fb69e141ce306d92dfe4b10e6cdc6e81d4fa910c30a846204dbcf8edf8; sha256=49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9 / 위치: 보존 파일 objects/sha256/49/49b6239650ee8d72235b1245e8c52b99587f0a7e85a8c44b2dba15db5ba126a9
보존 객체는 cookie/landing page이므로 서지 위치만 확인했고 본문 주장을 검증하지 못함.