Reporting Suspicious Activity Sample Clauses

Reporting Suspicious Activity. All Users must immediately report exposed or compromised passwords, keys, passphrases, or certificates, as well as any suspicious activity on an account. All suspicious activity must be reported to XXXXXX@xxx.xxx, whether or not compromise of an account or system is suspected.
AutoNDA by SimpleDocs
Reporting Suspicious Activity. If for any reason you believe that your Access Credentials, User ID, Password, personal or Account information may have been compromised, if you believe that activity has taken place in your Accounts without your permission or if you suspect any fraudulent activity in your Accounts, please notify us immediately by calling (000) 000-0000. You may also notify us in writing at Shell Federal Credit Union, P.O. Box 578, Deer Park, TX 77536-0578. Please refer to Shell FCU’s Electronic Funds Transfer Disclosure for information regarding error resolution. Shell FCU and/or third party service provider(s) make no representation that any content or use of Digital Banking is available outside of the United States. By accessing Digital Banking from locations outside of the United States, you do so at your own risk.
Reporting Suspicious Activity. If you notice any suspicious or unauthorised activity related to your Account, you should immediately report it to CoinFuze Customer Support. Prompt reporting will help protect the security of your Account and prevent potential losses.
Reporting Suspicious Activity. Introducing Firm must review transactions to detect suspicious activities. As soon as practicable after identifying suspicious activity, Introducing Firm shall notify Clearing Agent’s Anti-Money Laundering Compliance Officer and shall communicate with Clearing Agent about the transaction for the purpose of sharing information, unless such sharing of information is prohibited by law. In addition, Introducing Firm shall promptly notify Clearing Agent regarding any account activity that Introducing Firm reasonably believes to be suspicious, not legitimate, or not having a reasonably apparent explanation.
Reporting Suspicious Activity. Neither HR Trader, nor any of its employees, officers, managers, members, brokers or agents will have any liability to you if HR Trader reports any suspicious activity in connection with your Account.
Reporting Suspicious Activity. Should you encounter any of these scenarios while working for us, you must report them promptly to your line manager, to the Company Anti-Corruption and Bribery Representative or by using the whistleblowing COP.

Related to Reporting Suspicious Activity

  • Reporting of Non-Force Majeure Events Each Party (the “Notifying Party”) shall notify the other Parties when the Notifying Party becomes aware of its inability to comply with the provisions of this Agreement for a reason other than a Force Majeure event. The Parties agree to cooperate with each other and provide necessary information regarding such inability to comply, including the date, duration, reason for the inability to comply, and corrective actions taken or planned to be taken with respect to such inability to comply. Notwithstanding the foregoing, notification, cooperation or information provided under this Article shall not entitle the Party receiving such notification to allege a cause for anticipatory breach of this Agreement.

  • Reporting Violations You must immediately report any known violation of the District’s applicable policies, Internet safe- ty plan, or acceptable use guidelines to the technology coordinator. You must report requests for personally identifying information, as well as any content or commu- nication that is abusive, obscene, pornographic, sexually oriented, threatening, harassing, damaging to another’s reputation, or illegal to the technology coordinator.

  • Reporting Compliance The Company is subject to, and is in full compliance in all material respects with, the reporting requirements of Section 13 and Section 15(d), as applicable, of the Exchange Act.

  • Additional Reporting Within seven days after the date of this Agreement, the Recipient shall register in XXX.xxx, and thereafter maintain the currency of the information in XXX.xxx until at least October 1, 2022. The Recipient shall review and update such information at least annually after the initial registration, and more frequently if required by changes in the Recipient’s information. The Recipient agrees that this Agreement and information related thereto, including the Maximum Awardable Amount and any executive total compensation reported pursuant to paragraph 38, may be made available to the public through a U.S. Government website, including XXX.xxx.

  • Diversity Reporting Upon request, the Contractor will report to the Department its spend with business enterprises certified by the OSD. These reports must include the time period covered, the name and Federal Employer Identification Number of each business enterprise utilized during the period, commodities and contractual services provided by the business enterprise, and the amount paid to the business enterprise on behalf of each agency purchasing under the Contract.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!