DCI Specs - Digital Cinema Initiatives

• Be designed such that their firmware cannot be modified without the knowledgeand permission of the original manufacturer.• Require a Digital Cinema compliant certificate that authenticates and confirmsthe identity of the authority figure responsible for making a firmware change, andshall include time/date and version number information associated with anyfirmware change, in addition to the authority figure.• Not undergo firmware changes without informing potentially affected informationbases that support Digital Cinema equipment operations (e.g., databases usedby stakeholders for facility lists, KDM and TDL creation), and the owner of thedevice.• Log the firmware change event by meeting FIPS 140-2 Operational Environment(row 6 of Table 20: Summary of FIPS 140-2 Security Requirements)audit/recording requirements of the Operating System Requirements subsectionSecurity Level 3, except that Common Criteria (CC) and Evaluation AssuranceLevel (EAL) certification mandates shall not be required. The requirements forFIPS Level 3 audit/recording are encouraged but shall be optional.• Enable the extraction of the above firmware change related log records usingstandard log record messages per Section 9.4.6.3 Logging Subsystem. For thedelivery of these log records, it shall be mandatory that the records be signed..• Follow FIPS 140-2 certification body change notification requirements regardingmodifications to security devices. Undergo re-certification if required.9.5.3. Screen Management System (SMS)There are no physical constraints or requirements imposed on the SMS by the securitysystem (i.e., no SPB requirements); however, the SMS implementation shall not otherwiseweaken or effect the security operations of other Security Entities or SPBs.9.5.4. Subtitle ProcessingSubtitle encryption is directed primarily against interception during transport, andcryptographic protection within the theater is not required. Thus there are no protectionrequirements imposed on subtitle post-decryption processes, other than its implementationshall not weaken or otherwise effect the security operations of other Security Entities orSPBs.As an alternative to encryption of subtitle essence, the Composition Playlist (CPL)SubtitleTrackFileAssetType “Hash” element may be used to validate the integrity of receivedsubtitle content that has not been encrypted. The optional subtitle hash element, if used,shall be present and in the same signed CPL used for the image and audio. This integritycheck could be performed by the Security Manager, but may also be performed externally tothe IMB by, for example, the SMS.9.5.5. Compliance Testing and CertificationCompliance Testing is the process of qualifying Secure Processing Blocks (SPBs) and theirSecurity Entities for use in Digital Cinema systems. All SPBs shall be subject to qualifyingcriteria in the following areas:• Compliance to Intra-Theater Messaging (ITM) specifications – The SPB and internallogical SEs shall interpret and respond to the standard ITM message set accordingDCI Digital Cinema System Specification v.1.2 Page 141