PRIVACY PROTECTION ISSUES IN USER REQUIREMENTS COLLECTION Sample Clauses

PRIVACY PROTECTION ISSUES IN USER REQUIREMENTS COLLECTION. The procedure with which the project will define SPIDER's requirements as part of WP2 is to gather requirements from the relevant SPIDER stakeholders which, in turn, will specify the exact kind of user involvement. Each use case corresponds to a specific stakeholder and will be driven by a specific partner that will adopt the appropriate procedures for participation of humans. The WP2 activities that could potentially involve personal data collection and processing as well as informed consent procedures are those related to Task 2.1 “Analysis of User and Cybersecurity Requirements”. This task has the primary goal to specify the different types of users of the SPIDER platform, considering both cyber security experts as well as non-experts, using different real users' profiles with a variety of expertise and multiple professional orientations. In the context of T2.1, the different types of users and organizations that could benefit from the SPIDER platform solution have been identified. Five major stakeholder categories have been derived in total to specify the various uses cases with the objective to collect user requirements. These are: • Cybersecurity Professionals • Telecommunication Operators • Telecommunication Infrastructure Providers • Investment Management Positions • Individual Telecommunication Users A detailed description of the planned activities as well as considerations regarding the collection and processing of personal data associated with the user requirements elicitation process can be found in the Deliverable D9.8 (“POPD-Requirement No. 8”). The analysis includes considerations for the measures that should be adopted, if applicable, like anonymization techniques in the submitted online questionnaire, to allow for the adoption of the approach presented in the Deliverable D9.1 (“H-Requirement No. 1”). In D9.1, it is indicated in more details that the participants involved in the requirement elicitation process can be selected within the staff of SPIDER partners, or closely related network of experts, without the need of informed consent, as appropriate and applicable each time, as no personal data will be collected to the least extent possible. Indeed, the questionnaires to be distributed to the research participants will be completely anonymous and will not require any personal data from the participant. The participants will not be asked to login nor to submit their email addresses (or any other personal information) in order to take part...
AutoNDA by SimpleDocs

Related to PRIVACY PROTECTION ISSUES IN USER REQUIREMENTS COLLECTION

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

  • Customer Requirements Customer will be required to maintain complex passwords for their User accounts where applicable. For any such passwords LightEdge will provide a secure URL that any User can access to change passwords. All User passwords are set to a ninety (90) day password expiration schedule by default. LightEdge is not responsible for unexpected use of Services whether by ex-employees, compromised User passwords or any other misuse of Customer accounts. Customer shall be responsible for all costs incurred by such unexpected use of Service. Customer shall be fully responsible for providing to LightEdge at Customer’s own expense and in a timely manner the following: - All security for its Services and systems used or accessible in connection with Service; - Cooperative testing of all Customer-provided hardware, software, and Services for compatibility with Service; - Designating an Authorized Contact(s) to be the point of contact to interface with LightEdge Technical Support; - All cabling necessary to support Service; and - Physical and remote management access to any and all Servers onto which Service is installed.

  • Contractor Requirements The Firm shall be construed, during the entire term of this contract, to be an independent contractor. Nothing in this contract is intended to nor shall be construed to create an employer- employee relationship, or a joint venture relationship. The Firm represents that it is qualified to perform the duties to be performed under this contract and that it has, or will secure, if needed, at its own expense, applicable personnel who are qualified to perform the duties required under this contract. Such personnel shall not be deemed in any way, directly or indirectly, expressly or by implication, to be employees of the District. Any person assigned by the firm to perform the services hereunder shall be the employee or a subcontractor of the Firm, who shall have the sole right to hire and discharge its employee or subcontractors. The Firm or its subcontractors shall pay, when due, all salaries and wages of their employees and accepts exclusive responsibility for the payment of federal income tax, social security, unemployment compensation and any other withholdings that may be required. Neither the Firm, its subcontractors nor their employees are entitled to state retirement or leave benefits. It is further understood that the consideration expressed herein constitutes full and complete compensation for all services and performance hereunder, and that any sum due and payable to the Firm shall be paid as a gross sum with no withholdings or deductions being made by the District for any purpose from said contract sum, except as permitted in paragraphs 16, 17 and 18.

  • Accessibility Requirements Under Tex. Gov’t Code Chapter 2054, Subchapter M, and implementing rules of the Texas Department of Information Resources, the System Agency must procure Products and services that comply with the Accessibility Standards when those Products are available in the commercial marketplace or when those Products are developed in response to a procurement solicitation. Accordingly, Grantee must provide electronic and information resources and associated Product documentation and technical support that comply with the Accessibility Standards.

  • Facility Requirements 1. Maintain wheelchair accessibility to program activities according to governing law, including the Americans With Disabilities Act (ADA), as applicable. 2. Provide service site(s) that will promote attainment of Contractor’s program objectives. Arrange the physical environment to support those activities. 3. Decrease program costs when possible by procuring items at no cost from County surplus stores and by accepting delivery of such items by County.

  • Compliance with Safeguarding Customer Information Requirements The Servicer has implemented and will maintain security measures designed to meet the objectives of the Interagency Guidelines Establishing Standards for Safeguarding Customer Information published in final form on February 1, 2001, 66 Fed. Reg. 8616, and the rules promulgated thereunder, as amended from time to time (the “Guidelines”). The Servicer shall promptly provide the Seller information regarding the implementation of such security measures upon the reasonable request of the Seller.

  • Privacy Protection The Grantee shall comply with all applicable federal and state privacy laws, including Section 631 of the Cable Act and regulations adopted pursuant thereto.

  • Emergency Procedures All residents and guests are required to exit the building during emergencies that require evacuation and follow instructions given by authorized University emergency personnel (e.g., Security Services, Emergency Response Wardens and Building Emergency Captains). Residents and guests FIRE PROCEDURES AND FIRE ALARMS: All residents and guest(s) are required to exit the residences at the sound of a fire alarm. In the event of fire, residents and guest(s) are required to follow instruction given by Fire Services personnel.

  • E-Verify Requirements To the extent applicable under ARIZ. REV. STAT. § 41- 4401, the Contractor and its subcontractors warrant compliance with all federal immigration laws and regulations that relate to their employees and their compliance with the E-verify requirements under ARIZ. REV. STAT. § 23-214(A). Contractor’s or its subcontractor’s failure to comply with such warranty shall be deemed a material breach of this Agreement and may result in the termination of this Agreement by the City.

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse. B. Grantee shall use the Texas Abuse Hotline Website located at xxxxx://xxx.xxxxxxxxxxxxxx.xxx/Login/Default.aspx as required by the System Agency. Grantee shall retain reporting documentation on site and make it available for inspection by the System Agency.

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