Application Hardening Clause Samples

The Application Hardening clause requires that software applications be designed and implemented with enhanced security measures to resist tampering, reverse engineering, and other forms of unauthorized access or modification. This typically involves integrating techniques such as code obfuscation, anti-debugging tools, and runtime integrity checks into the application. By mandating these protections, the clause helps safeguard sensitive data and intellectual property, reducing the risk of security breaches and ensuring the application's resilience against malicious attacks.
POPULAR SAMPLE Copied 2 times
Application Hardening. Supplier will comply with this Section 15.5 if Supplier is providing Accenture with access to or the use of any software, including software-as-a-service or cloud-based software. Supplier will maintain and implement secure application development policies, procedures, and standards that are aligned to Industry Standard practices (e.g., SANS Top 35 Security Development Techniques and Common Security Errors in Programming and the OWASP Top Ten project). This applies to web application, mobile application, embedded software, and firmware development. All Personnel responsible for application design, development, configuration, testing, and deployment will be qualified to perform such activities and receive appropriate training on such policies, procedures, and standards.
View SourceView Similar (62)
Application Hardening i) Jamf will maintain and implement secure application development policies, procedures and standards that are aligned to Industry Standard practices such as the SANS Top 25 Security Development Techniques or the OWASP Top Ten project. ii) All personnel responsible for secure application design, development, configuration, testing, and deployment will be qualified to perform the Services and receive appropriate training regarding Jamf’s secure application development practices.
View SourceView Similar (7)
Application Hardening. Supplier will comply with this Section if Supplier is providing Accenture with access to or the use of any software, including software-as-a-service or cloud-based software. Supplier will maintain and implement secure application development policies, procedures, and standards that are aligned to Industry Standard practices (e.g., SANS Top 35
View SourceView Similar (3)
Application Hardening i. Provider will maintain and implement secure application development policies, procedures, and standards that are aligned to Industry Standard practices such as the SANS Top 25 Software Errors, the OWASP Top Ten project and the NIST Secure Software Development Framework (SSDF). This applies to web application, mobile application, embedded software, and firmware development as appropriate. ii. All personnel responsible for secure application design, development, configuration, testing, and deployment will be qualified to perform the Provider Services and receive appropriate training regarding Provider’s secure application development practices.
View SourceView Similar (2)
Application Hardening. From the viewpoint of WP5, in Task 5.2, we will set guidelines to improve code robustness, showcasing what is done with the CompBioMed software stack (see Appendix A of Deliverable 2.1 First Report on Fast Track Application Readiness [2]). Based on our own extensive experience with our own software, we will define good practices to enhance code robustness and stability, such as CI/CD (Continuous Integration/Continuous Development) integration (from basic ideas to complex pipelines), documentation, regression tests, performance tests, etc. We will showcase software deployment in HPC infrastructures to facilitate code access to users, assessing availability of suitable resources, access mechanisms and performance. We will define policies for dataset interoperability, selecting the proper formats, sources, location, etc. This data could include inputs for simulation codes, output of simulations for clinical analysis, data assimilation and model improvement, anonymised clinical data, experimental measurements, etc.
View Source
Application Hardening i) We will maintain and implement secure application development policies, procedures, and standards that are aligned to Industry Standard practices such as the SANS Top 25 Security Development Techniques or the OWASP Top Ten project. ii) All personnel responsible for secure application design, development, configuration, testing, and deployment will be qualified to perform the Services and receive appropriate training regarding our secure application development practices.
View Source
Application Hardening. Supplier will comply with this Section
View Source
Application Hardening. Supplier will comply with this Section 12.5 if Supplier is providing Accenture with access to or the use of any software, including software-as-a-service or cloud-based software. Supplier will maintain and implement secure application development policies, procedures, and standards that are aligned to Industry Standard practices (e.g., SANS Top 35 Security Development Techniques and Common Security Errors in Programming and the OWASP Top Ten project). This applies to web application, mobile application, embedded software, and firmware development. All Personnel (In this Section 12, “Personnel” means Supplier’s personnel, its contractors, and its agents.) responsible for application design, development, configuration, testing, and deployment will be qualified to perform such activities and receive appropriate training on such policies, procedures, and standards.
View Source
Application Hardening. For all software running on a device, as with the device itself, the principle of least privilege (or whitelisting) should be applied. Inputs from the outside should be sanitized; especially involved databases should possess protection measures against SQL injection [41]. In addition, similar to device hardening (4.1.8), rate limiting should be imposed. This would mean to restrict the number of connections and/or queries from a single source per time.
View Source

Related to Application Hardening

  • Removal of Improvements All alterations, additions and other improvements by Tenant shall become the property of Landlord and shall not be removed from the Project, unless request is made by Landlord to Tenant to remove those alterations, additions and other improvements which were made without Landlord's approval where such approval was required under this Lease. All (i) moveable trade fixtures and signs installed in the Project by Tenant and paid for by Tenant, other than those items comprising FF&E or Operating Equipment which are replacements, substitutions or additions thereof or thereto made by Tenant and FF&E and Operating Equipment present in the Project as of the date hereof, and (ii) signs, logos and other property, including Operating Equipment and Supplies, bearing the logo of any Franchisor which is not continuing as the Franchisor following the expiration of the Term of this Lease shall remain the property of Tenant or Franchisor, as the case may be, and may be removed upon the expiration of the Lease Term; provided that any of such items as are affixed to the Project and require severance may be removed only if Tenant repairs any damage caused by such removal and that Tenant shall have fully performed all of the terms, conditions and covenants to be performed by Tenant under this Lease. If Tenant fails to remove such items from the Project by the expiration of the Lease Term or earlier termination of this Lease, all such trade fixtures, furniture, furnishings and signs shall become the property of Landlord, unless Landlord elects to require their removal, in which case Tenant shall, at its sole cost and expense, promptly remove the same and restore the Project to its condition on the date of this Lease. The covenants contained in this Section shall survive the expiration or earlier termination of this Lease.

  • SCOPE OF ARCHITECT’S BASIC SERVICES 3.1 The Architect’s Basic Services consist of those described in this Article 3 and include usual and customary structural, mechanical, and electrical engineering services. Services not set forth in this Article 3 are Supplemental or Additional Services. § 3.1.1 The Architect shall manage the Architect’s services, research applicable design criteria, attend Project meetings, communicate with members of the Project team, and report progress to the Owner. § 3.1.2 The Architect shall coordinate its services with those services provided by the Owner and the Owner’s consultants. The Architect shall be entitled to rely on, and shall not be responsible for, the accuracy, completeness, and timeliness of, services and information furnished by the Owner and the Owner’s consultants. The Architect shall provide prompt written notice to the Owner if the Architect becomes aware of any error, omission, or inconsistency in such services or information. § 3.1.3 As soon as practicable after the date of this Agreement, the Architect shall submit for the Owner’s approval a schedule for the performance of the Architect’s services. The schedule initially shall include anticipated dates for the commencement of construction and for Substantial Completion of the Work as set forth in the Initial Information. The schedule shall include allowances for periods of time required for the Owner’s review, for the performance of the Owner’s consultants, and for approval of submissions by authorities having jurisdiction over the Project. Once approved by the Owner, time limits established by the schedule shall not, except for reasonable cause, be exceeded by the Architect or Owner. With the Owner’s approval, the Architect shall adjust the schedule, if necessary, as the Project proceeds until the commencement of construction. § 3.1.4 The Architect shall not be responsible for an Owner’s directive or substitution, or for the Owner’s acceptance of non-conforming Work, made or given without the Architect’s written approval. § 3.1.5 The Architect shall contact governmental authorities required to approve the Construction Documents and entities providing utility services to the Project. The Architect shall respond to applicable design requirements imposed by those authorities and entities. § 3.1.6 The Architect shall assist the Owner in connection with the Owner’s responsibility for filing documents required for the approval of governmental authorities having jurisdiction over the Project.

  • Demolition The Lessor shall remove existing abandoned electric, telephone, and data cabling and devices, as well as any other improvements or fixtures in place, to accommodate the Government’s requirements. Any demolition of existing improvements that is necessary to satisfy the Government’s layout shall be done at the Lessor’s expense.

  • Application Process The employees wishing to enter into a job share arrangement will apply in writing to the Employer and forward a copy to the Union outlining the proposed commencement date of the job share, how the hours and days of work will be shared and how communication and continuity of work will be maintained. The Employer shall communicate a decision on a job share request in writing to the applicants. Applications to Job Sharing shall not be unreasonably denied.