Security Vulnerability means a flaw or weakness in system security procedures, design, implementation, or internal controls that could be exercised (accidentally triggered or intentionally exploited) and result in a security breach such that data is compromised, manipulated or stolen or the system damaged.
Security Vulnerability means a weakness in software code, a product or a system that leaves it open to the potential for exploitation in the form of unauthorized access or malicious behavior.
Security Vulnerability means any attribute of hardware, software, process, or procedure that could enable or facilitate the defeat of a security control. 6 U.S.C. 1501(17)
Examples of Security Vulnerability in a sentence
While no software can be guaranteed to be free from Security Vulnerabilities, if a Security Vulnerability is discovered, Motorola will take the steps set forth in Section 6 of this Agreement.
More Definitions of Security Vulnerability
Security Vulnerability. ’ means any attribute of hard-
Security Vulnerability means any attribute of hardware, software,
Security Vulnerability means a state in the design, coding, implementation, operation or management of a Deliverable that allows an attack by a party that could result in unauthorized access or exploitation, including without limitation (1) access to, controlling or disrupting operation of a system; (2) access to, deleting, altering or extracting data or (3) changes of identity, authorizations or permissions of users or administrators. A Security Vulnerability may exist regardless of whether a Common Vulnerabilities or Exposures (CVE) ID or any other scoring or official classification has been assigned to it.
Security Vulnerability means a weakness or flaw in a software product or system’s design, operation or implementation that could be exploited by an attacker to violate the software product or system’s security or privacy policies, including without limitation, a flaw that makes it infeasible, even when the product is properly used, to prevent an attacker from usurping privileges on a user’s system, compromising its data, security or other operational features. If you become aware that your Application can cause a Security Vulnerability, you agree to (1) immediately notify Intel, (2) take immediate measures to stop the internal distribution of your Application, (3) promptly correct such Security Vulnerability and (4) indemnify Intel for any claims that may be alleged against Intel due to such Security Vulnerability.
Security Vulnerability means a weakness in software code, a product or a system that leaves it open to the potential for exploitation in the form of unauthorized access or malicious behaviour. “Service Hours”, “SH” means the service hours purchased by the Customer in the applicable Order. "Service Levels" means the service levels set out in sections 4.4 and 5.9 below. “Software” means the IFS Software and/or CB Apps Software. “Support Ticket” means a Customer request for support initiated by the Customer through the CB Ticket Portal. "Ticket Portal" means the CB ticketing system where Customer's nominated contacts will submit Support Tickets. “Updates” means a cumulative set of fixes and improvements for a release. Updates are compatible with a specific release of the Software as designated by IFS and/or CB and released in accordance with their release schedule as applicable from time to time. "Workaround" means reducing or eliminating the impact of a Defect for which a full resolution is not yet available, normally in agreement with the Customer. For Priority 1 and 2 Defects a workaround would mean a solution where the Defect is no longer Priority 1 or 2.
Security Vulnerability is a flaw or weakness in a system's design, implementation, or operation and management that could be exploited to violate the system's security policy. Learnmetrics will notify Your Designated Security Contact of newly discovered security vulnerabilities within any products or services supplied by Learnmetrics as part of this agreement within a commercially reasonable time following Learnmetrics becoming aware of them. This notification will be done via email communication which will include the details of the possible risk and an action plan for resolution of the vulnerability, as described below, if not already resolved. In the event of a critical security vulnerability determined to be directly applicable to Your use of the contracted product(s) or service(s), Learnmetrics will contact Your Designated Security Contact by e-mail or telephone. Telephone notification does not supersede or relieve Learnmetrics from the obligation to provide the detailed e-mail notification described above. If security issues are discovered or reasonably suspected by You, Learnmetrics shall assist You in performing an investigation to determine the nature of the issue. In the event that said investigation determines that an actual security vulnerability exists, Learnmetrics will develop an action plan for resolving the vulnerability as described below. Learnmetrics will provide to You an action plan for resolution of security vulnerabilities. Each action plan should include the following information: • Problem statement(s), including early evaluation of possible resolution • Confirmation, when possible, that Learnmetrics can reproduce the problem • Problem status • Actions required for resolution • Who needs to perform the actions (where "who" may refer to Learnmetrics, You, third parties, etc.) • Projected date for resolution.
Security Vulnerability is a set of conditions that leads or may lead to an implicit or explicit failure of the confidentiality, integrity or availability of a system. Security Vulnerabilities include, but are not limited to: (i) Executing commands as another user; (ii) Accessing data in excess of specified or expected permission; (iii) Posing as another user or service within a system; (iv) Causing an abnormal denial of service; (v) destroying data without permission; or (vi) Exploiting an encryption implementation weakness that significantly reduces the time or computation required to recover the plaintext from an encrypted message. Principal shall follow industry-standard software assurance practices (such as standards developed by XXXXXxxx.xxx, ISO or any successor or similar industry organization) to minimize the risk of Security Vulnerabilities being introduced in the Pivotal Software provided to Agent at any point in the product lifecycle. Upon external discovery (including, without limitation, by Agent or one of its customers) of any Security Vulnerability in the Pivotal Software, Principal shall follow industry best practices for handling and responding to vulnerabilities such as ISO Standards 29147 and 30111.