10.46243/jst.2021.v6.i05.pp146-167 registered
The State-of-the-Art in IC Reverse Engineering
Resolves to https://www.jst.org.in/index.php/pub/article/view/926
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2021.v6.i05.pp146-167
Registered 29 Sep 2026 via crossref · record version 2 · last change 30 Sep 2026, 12:00 AM · record sha256 93a91e971ccec9bd…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
The State-of-the-Art in IC Reverse Engineering (PrincipalTitle)
Published 2021-10-29
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 06 · issue 05 · pages 146–167
Agents
- G Shobha (author)
- B Swetha (author)
- V David (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2021.v6.i05.pp146-167
Abstract
This paper gives an overview of the place of reverse engi- neering (RE) in the semiconductor industry, and the techniques used to obtain information from semiconductor products. The continuous drive of Moores law to increase the integration levelof silicon chips has presented major challenges to the reverse engineer, obsolescing simple teardowns, and demanding the adoption of new and more sophisticated technology to analyse chips. Hardware encryption embedded in chips adds a whole other level of difficulty to IC analysis. This paper covers product teardowns, and discusses the techniques used for system-level analysis, both hardware and software; circuit extraction, taking the chip down to the transistor level, and working back up through the interconnects to create schematics; and process analysis, looking athow a chip is made, and what it is made of. Examples are also given of each type of RE. The paper concludes with a case study of the analysisof an IC with embedded encryption hardware.
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2021.v6.i05.pp146-167 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | The State-of-the-Art in IC Reverse Engineering (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: G Shobha author: B Swetha author: V David publisher: Longman Publishers published: 2021-10-29 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 06 · no. 05 · pp. 146–167 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2026-09-12 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 79 fields set · sha256 172ba0b1b244… |
| 2 | 30 Sep 2026, 12:00 AM | update record re-read from api.crossref.org | Administrator (admin) | container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
