Xerox M118i Statement of Volatility - Page 3

See Type of Memory - used

Page 3 highlights

Certificate of Volatility 6. Method of access: How is it accessed? Is non-volatile memory location theoretically accessible with any system code, not just via the operating system or low level booting firmware? Marking Engine non-volatile memory is used for storing Multifunction Device application settings and is accessible by application level code. There is no user access to the memory devices, except as provided programmatically to control device behaviors 7. Warranty: Does chip removal or EEPROM erasure void the warranty? Yes, memory removal or erasure will void the warranty 8. Size: How much memory is contained? Number of bytes, etc. See section 1, "Type of Memory" 9. Spacing: Is the memory fully utilized or does it have available memory space for additional information to be placed? The non-volatile memory devices are sized to contain the necessary amount of data required for system operation. Usually there are some unused memory addresses where additional information could be theoretically stored. Without access to the software developers' memory maps, determining the location of this unused memory would require reverse engineering the software. 10. Can this non-volatile memory be addressed to ensure that only authorized information is resident? If yes, how? At boot-up, the system computes a checksum for each non-volatile memory device. (Note: The computed checksum is compared against a value stored in the device itself. This is sufficient to detect hardware failures, but not necessarily intentional corruption.) Version of 17-Oct-06 Page 3 of 3

  • 1
  • 2
  • 3

Certificate of Volatility
Version of 17-Oct-06
Page 3 of
3
6.
Method of access: How is it accessed? Is non-volatile memory location theoretically accessible with
any system code, not just via the operating system or low level booting firmware?
Marking Engine non-volatile memory is used for storing Multifunction Device application settings and
is accessible by application level code. There is no user access to the memory devices, except as
provided programmatically to control device behaviors
7.
Warranty: Does chip removal or EEPROM erasure void the warranty?
Yes, memory removal or erasure will void the warranty
8.
Size: How much memory is contained? Number of bytes, etc.
See section 1, “Type of Memory”
9.
Spacing: Is the memory fully utilized or does it have available memory space for additional
information to be placed?
The non-volatile memory devices are sized to contain the necessary amount of data required for
system operation. Usually there are some unused memory addresses where additional information
could be theoretically stored. Without access to the software developers’ memory maps, determining
the location of this unused memory would require reverse engineering the software.
10. Can this non-volatile memory be addressed to ensure that only authorized information is resident? If
yes, how?
At boot-up, the system computes a checksum for each non-volatile memory device. (Note: The
computed checksum is compared against a value stored in the device itself. This is sufficient to
detect hardware failures, but not necessarily intentional corruption.)