You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should define an experimental protocol to disassemble and gather information (i.e., recon) of the device in question. As a preliminary list of things I want to keep track of:
The disassembly of the physical build (e.g., the case). Identify part numbers, build identifiers revision identifiers
Pictures of the surface-level PCB with as much track information as possible. Board revisions may be tagged somehow (e.g., using the rev. x.x synax). Try to find these
Any tags on possible chips part numbers or major components:
Any CPU/SOC
Flash or storage
RF/Wireless/network chips
Any other peripherals of interest (e.g., a camera or LED)
Any suspect headers (with our without pins). Ideally, any tags of candidate JTAG/UART ports would be A+
Any other information to build device SBOM would also be great (e.g., if we know what possible software pieces are there in terms of OS/Libraries available). This can be generally found in the manufacturer's website.
As a first approach. I'd want us to have a Yaml template so that we can fill this in in a structured fashion for ensuing devices.
The text was updated successfully, but these errors were encountered:
We should define an experimental protocol to disassemble and gather information (i.e., recon) of the device in question. As a preliminary list of things I want to keep track of:
Any other information to build device SBOM would also be great (e.g., if we know what possible software pieces are there in terms of OS/Libraries available). This can be generally found in the manufacturer's website.
As a first approach. I'd want us to have a Yaml template so that we can fill this in in a structured fashion for ensuing devices.
The text was updated successfully, but these errors were encountered: