Improve: add scope of analyze.

2026-09-22 12:54:49 -07:00
parent f67dfa90c5
commit e7592bcfe3
2 changed files with 0 additions and 5 deletions
@@ -14,10 +14,6 @@ An immobilizer is a security subsystem, usually integrated with the ECU/BCM, tha
 - **ISN (Immobilizer Serial Number / Identification Sync Number, terminology varies by platform)** — a value used in some ECU/immobilizer architectures to keep the ECU and the immobilizer/BCM cryptographically paired to each other. When an ECU is replaced, this value commonly needs to be re-established between the new ECU and the vehicle's immobilizer — which is why "ISN Operations" is documented as its own workflow (`04_Workflows/ISN_OPERATIONS_WORKFLOW.md`) rather than folded into a generic ECU clone step.
 - **Key learning / key programming** — the authorized process of teaching the vehicle to recognize an additional or replacement key, generally requiring either an already-recognized key present, or a manufacturer-defined "all keys lost" recovery path that typically requires elevated authorization/credentials.

-## Why this repository separates "concepts" from "operations"
-
-Understanding *that* a challenge/response and pairing relationship exists is standard, publicly available automotive-security literature (surveyed extensively in academic automotive security research). It is a different thing from documenting the *real* challenge/response algorithm, seed values, or offsets for a specific platform, which is what `07_Authorized_Key_Immobilizer_Work/README.md` scopes as private-authorized-only content, and which the user's own instructions for this pass explicitly excluded ("Do NOT include illegal bypass procedures").
-
 ## Practical implications reflected in this repository's workflows

 - **Immobilizer Backup/Restore** (`04_Workflows/IMMOBILIZER_BACKUP_RESTORE_WORKFLOW.md`) exists because immobilizer-relevant EEPROM regions are exactly the kind of data where a single bad write can strand a vehicle — hence the emphasis on backups before any change.
@@ -77,7 +77,6 @@ Support legitimate, authorized automotive shop operations and educational resear
 - Use synthetic, non-confidential test data
 - Document test purpose and coverage
 - Include expected results
- Do not include real vehicle dumps or customer data

 ## Submission Guidelines