Scope of Audit. Customer shall provide at least sixty days advance notice of any audit unless mandatory Data Protection Law or a competent data protection authority requires shorter notice. The frequency and scope of any audits shall be mutually agreed between the parties acting reasonably and in good faith. Customer audits shall be limited in time to a maximum of three business days. Beyond such restrictions, the parties will use current certifications or other audit reports to avoid or minimize repetitive audits. Customer shall provide the results of any audit to SAP.
Scope of Audit. The scope of the audit shall be limited to the services provided and/or purchased by the Parties and the associated charges, books, records, data and other documents relating thereto for the period which is the shorter of (i) the period subsequent to the last day of the period covered by the audit which was last performed (or if no audit has been performed, the Effective Date) and (ii) the twelve (12) month period immediately preceding the date the Audited Party received notice of such requested audit.
Scope of Audit. Head End Audit: · Operator should provide Complete Accurate Schematic Diagram of their Head End, Earth Stations, Systems and Processes for Audit and Auditing Purpose. · Operator to submit and confirm the no. of MUX’s (Multiplexer Units) installed with active TS (Transport Stream) outputs. This should include physical audit of head end, earth station and analysis of TS stream from the Mux. · All TS from MUX should be encrypted for the Territory. · Operator to ensure that his network watermark logo is inserted on all pay channels at encoder end only. · All pay channels IRDs to be provided to Operator by the Broadcaster should have SDI/Composite/ SDI output only. The Broadcaster should not give IRDs with ASI/IP output or CAM Module. CAS Audit: Operator to provide all below information correctly: · Make and version of CAS installed at Head End. · CA system certificate (with version Information) to be provided by Operator. · CA system must install the previous version update, and road map to install the upcoming update. · CAS version installed should not have any history of hacking, certificate from CAS vendor required. · CAS system should support at least 1 (one) million subscribers. CAS vendor should provide certificate. · CAS should be able to generate log of all activities i.e. activation/deactivation/FP/OSD. · CAS should be able to generate active/deactivate report channel wise/package wise. · STB’s SOC and smart cards to be uniquely paired from Operator before distributing box down the line. · Operator to declare by undertaking the no of encryptions CAS/SMS he is using at the head end and in future if he is integrating any additional CAS/SMS same should be notified to the Broadcaster by means of a fresh undertaking. · Reconciliation of CAS database (active cards, service wise and package wise) with SMS database to be provided by Operator. CAS vendor required to certified reconciliation of data. · No activation / deactivation from direct CAS system, it must be routed via SMS client only. · Operator should provide CAS vendor certified copies of active/deactivate channel wise/product wise report and Package/product report during audit period. · CA system should have the capability of providing history of all actions taken for last 2 (two) years. SMS Audit: · All product authorization must be originated from SMS only. Only after origination from SMS, the CAS should be communicated in this regard. · SMS and CAS should be fully integrated for all the logics (in...
Scope of Audit. Customer shall provide at least sixty days advance notice of any audit unless mandatory Data Protection Law or a competent data protection authority requires shorter notice. The frequency and scope of any audits shall be mutually agreed between the parties acting reasonably and in good faith. Customer audits shall be limited in time to a maximum of three business days. Beyond such restrictions, the parties will use current certifications or other audit reports to avoid or minimize repetitive audits. Customer shall provide the results of any audit to SAP. 감사 범위. 고객은 의무적인 정보 보호 법률 또는 관련 정보 보호 당국이 더 짧은 기간의 통지를 요구하지 않는 한 모든 감사에 대해 적어도 60 일의 사전 통지를 제공해야 합니다. 감사의 빈도와 범위는 합리적이고 성실하게 행동하는 당사자들 간에 상호 합의되어야 합니다. 고객 감사는 최대 3 근무일의 기간으로 제한됩니다. 이러한 제한사항 외에도, 당사자들은 기존 인증서 또는 다른 감사 보고서를 이용해 감사 중복을 최소화합니다. 고객은 모든 감사 결과를 SAP 에 제공합니다.
Scope of Audit. I. Head End Audit MSO should provide Complete Accurate Schematic Diagram of all their Head Ends (Back up/Mini, etc), Earth Stations, Systems and Processes for Audit and Auditing Purpose. • MSO to submit & confirm the no. of MUX’s (Multiplexer Units) installed with active TS (Transport Stream) outputs. This should include physical audit of head end, earth station and analysis of TS stream from the Mux. • Perform checks on IP configuration to confirm and identify live and proxy servers. This shall include IP credentials of all the servers include MUX • All TS from MUX should be encrypted for the territory. • MSO to ensure that his Network Watermark logo is inserted on all Pay Channels at encoder end only as per requirements defined in Annexure IX. • Take inventory IRDs + VCs installed in each head-ends including their serial numbers. Make note of broadcaster IRDs + VCs available but not installed. • Check MUX configuration to validate number of Transport Streams (“TS”) configured with SID, scrambling status of each SID and ECM and EMM configuration. • Take screenshot of all Transport Streams from MUX and compare with results of field TS recording. • Take information of QAMs installed and powered to identify streams available for local insertion by LCOs. • Use FTA cable box/ TS analyser to confirm whether all channels are encrypted
Scope of Audit. The scope of the audit shall be limited to the services provided and/or purchased by the Parties and the associated charges, books, records, data and other documents relating thereto for the period which is the shorter of
Scope of Audit. Customer shall provide at least sixty days advance notice of any audit unless mandatory Data Protection Law or a competent data protection authority requires shorter notice. The frequency and scope of any audits shall be mutually agreed between the parties acting reasonably and in good faith. Customer audits shall be limited in time to a maximum of three business days. Beyond such restrictions, the parties will use current certifications or other audit reports to avoid or minimize repetitive audits. Customer shall provide the results of any audit to SAP./ Ruang Lingkup Audit. Pelanggan harus menyampaikan pemberitahuan sekurang-kurangnya enam puluh hari di muka tentang audit apa pun kecuali jika Undang-undang Perlindungan Data wajib atau otoritas perlindungan data yang kompeten memerlukan pemberitahuan yang lebih singkat. Frekuensi dan ruang lingkup dari setiap audit harus disepakati bersama antara pihak- pihak yang bertindak secara wajar dan dengan iktikad baik. Waktu audit pelanggan harus dibatasi hingga maksimal tiga hari kerja. Di luar pembatasan tersebut, para pihak akan menggunakan sertifikasi saat ini atau laporan audit lainnya untuk menghindari atau meminimalkan audit berulang. Pelanggan harus menyampaikan hasil audit kepada SAP.
Scope of Audit. Customer shall provide at least sixty days advance notice of any audit unless mandatory Data Protection Law or a competent data protection authority requires shorter notice. The frequency and scope of any audits shall be mutually agreed between the parties acting reasonably and in good faith. Customer audits shall be limited in time to a maximum of three business days. Beyond such restrictions, the parties will use current certifications or other audit reports to avoid or minimize repetitive audits. Customer shall provide the results of any audit to SAP. // 監査の範囲 顧客は、監査を行う場合には少なくとも 60 日前までに事前通知を行うものとする が、強制力のある「データ保護法」又はデータ保護当局によってより短期の通知が求められる場合はこの限 りではない。監査の頻度及び範囲は、両当事者間で、合理的にかつ誠意をもって相互に合意されるものとす る。顧客による監査は、最長で 3 営業日に限られるものとする。かかる制限を超えた場合、両当事者は最新 の証明書又はその他の監査報告書を利用して、反復的な監査を避ける又は最小限にするものとする。顧客は、監査の結果を SAP に提供するものとする
Scope of Audit. Customer shall provide at least sixty days advance notice of any audit unless mandatory Data Protection Law or a competent data protection authority requires shorter notice. The frequency and scope of any audits shall be mutually agreed between the parties acting reasonably and in good faith. Customer audits shall be limited in time to a maximum of three business days. Beyond such restrictions, the parties will use current certifications or other audit reports to avoid or minimize repetitive audits. Customer shall provide the results of any audit to SAP. // 監査✰範囲 顧客は、監査を行う場合には少なくとも 60 日前までに事前通知を行うも✰とするが、強制力✰ある「データ保護法」又はデータ保護当局によってより短期✰通知が求められる場合はこ✰限りではない。監査✰頻度及び範囲は、両当事者間で、合理的にかつ誠意をもって相互に合意されるも✰とする。顧客による監査は、最長で 3 営業日に限られるも✰とする。かかる制限を超えた場合、両当事者は最新 ✰証明書又はそ✰他✰監査報告書を利用して、反復的な監査を避ける又は最小限にするも✰とする。顧客は、監査✰結果を SAP に提供するも✰とする
Scope of Audit. Customer shall provide at least sixty (60) days advance notice of any audit unless mandatory Applicable Data Protection Laws or a competent data protection authority requires shorter notice. The frequency and scope of any audits shall be mutually agreed between the parties acting reasonably and in good faith. Customer audits shall be limited in time to a maximum of three business days. Notwithstanding the foregoing, if the physical data center(s) where the Personal Data is processed is not accessible to Customer, Provider will make available, via secure conference, various documents which attest to the security posture of such facility. Beyond such restrictions, the parties will use current certifications or other audit reports to avoid or minimize repetitive audits. Customer shall provide the results of any audit to Provider.
