Security Architecture Sample Clauses

Security Architecture. (a) Promptly address any security and privacy events as notified at xxxx://xxx.xxxxxx.xxx/security/security-bulletins/, except those categorized as “Informational”. (b) Monitor and evaluate software running in its AWS Enterprise Accounts for known and new vulnerabilities and take the steps necessary to address such vulnerabilities. (c) Configure AWS CloudTrail where available for all Services and implement appropriate retention, monitoring, and incident response processes using AWS CloudTrail logs. (d) Enable and configure Service-specific logging features where available for all Services and implement appropriate monitoring and incident response processes. For example, without limitation, where appropriate, Customer will enable access request logging features in Amazon Elastic Load Balancing, access request logging features in Amazon S3, database logging in Amazon Relational Database Service, and other logging features available in the Services. (e) Apply appropriate resource-based policies limiting access only to authorized parties to all Services where available.
AutoNDA by SimpleDocs
Security Architecture. Contractor specifically represents and warrants that with respect to Contractor-owned and/or controlled Hardware, Software and Environments, Contractor has established and during the term of this Agreement will at all times maintain: A security architecture that reasonably ensures implemented and effective NIST 800-53 security controls; A system of effective firewall(s) and intrusion detection technologies necessary to protect CDPH data; Appropriate network security design elements that provide for segregation of data; Procedures to encrypt information in transmission and storage; Procedures to ensure regular testing of Contractor'ssecurity systems and processes; Database and application layer design processes that ensure website applications are designed to protect CDPH data that is collected, processed, and transmitted through such systems.
Security Architecture. A security architecture has been devised and applied across the information resources of Veeva. The architecture comprises a defined set of security mechanisms and supporting standards.
Security Architecture. A structured and enforced security architecture covering all information resources, assets and standards of TikaMobile has been developed and applied to all lengths of the company.
Security Architecture. As the Smart Grid grows more complex and interconnected in the coming years, it is crucial that it is designed to be secure. A good security architecture is crucial. We see three important topics. First, how the operational technology (OT) systems, such as SCADA systems, smart metering systems and legacy systems, are connected first to the IT systems of DSOs, and then (indirectly) to the rest of the world. Second, how the WAN communications with the many devices spread over substations, homes, businesses, and other places are secured. And third, how access to the different components and sys- tems is controlled. • IT and OT networks connected in an ad hoc manner • WAN security relies on telecom network • Simple access control • Structured network zoning, e.g. following IEC 62443 • WAN communications encrypted and authenticated • Centralized access management • Security in the endpoints • End-to-end secure communications • Multi-stakeholder trust relations (using public key cryptogrpaphy)
Security Architecture. Development The purpose of the “Security Architecture Development” process is to develop a plan and set of principles that describe: (a) the security services that a system is required to provide to meet the needs of its users; (b) the system elements required to implement the services; and (c) the performance levels required in the elements to deal with the threat environment, (the “Security Architecture”). The Security Architecture Development process includes the following activities, as applicable: 1 Receiving the Security Policy; 2 Developing high level alternatives that comply with the Enterprise IT Architecture and selecting from among the alternatives, including by: (a) Identifying benefits, and potential risks and mitigating responses, for each alternative; (b) Documenting the rationale for using each alternative; and (c) Selecting the best alternative based on the foregoing. 3 Based on the alternative selected, completing Security Architecture deliverables identified by Enterprise IT Architecture, which may include: (a) Architecture level deliverables; (b) Conceptual level deliverables; (c) Solution level deliverables; and (d) Implementation level deliverables.
Security Architecture. Licensor is responsible for security of the Data Center including, but not limited to, servers, routers, firewalls, switches, circuits, and related software, and has deployed various types of defense against unauthorized access to the Data Center. Licensee-owned equipment that is connected to any Licensor-maintained device (e.g., border router, firewall) must comply with current Licensor requirements and standards, the current version of which are available upon request. Licensor will provide reasonable notice to Licensee of any change to the requirements or standards. Any anticipated changes to Licensee's environment that may affect the Hosting Services must be submitted in writing to Licensor for Licensor's review and approval at least one week prior to Licensee's scheduled implementation. If Licensee modifies its equipment or software configurations that result in any interruption of the Hosting Services, all diagnostic and repair time conducted by Licensor to restore connectivity will be billed to Licensee at Licensor's then-current rates. Upon Licensee's written request, Licensor will provide Licensee with a copy of the most recent independent security audit report (SAS 70) of Licensor's operations, provided that such SAS 70 report shall be treated as Licensor's Proprietary Information.
AutoNDA by SimpleDocs
Security Architecture. QBE and OnePath General shall demonstrate security architectural requirements are incorporated into their architecture proposals where the availability, integrity and confidentiality of relevant information may be impacted. Proposed security architecture must ensure that relevant information processed, stored and transmitted from information systems owned or managed by QBE or OnePath General are protected from internal and external threats.
Security Architecture 

Related to Security Architecture

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Security Technology When the service is accessed using a supported web browser, Secure Socket Layer (“SSL”), or equivalent technology shall be employed to protect data from unauthorized access. The service security measures shall include server authentication and data encryption. Provider shall host data pursuant to the DPA in an environment using a firewall that is periodically updated according to industry standards.

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