Difference between revisions of "Security flaw"

From Clinfowiki
Jump to: navigation, search
Line 1: Line 1:
Security flaws can be a weakness in the design of an application or in the procedures in using an application. Also a security flaw can be know or unknown. With known security flaws it may be possible to create procedure to mitigate those know weaknesses. With unknown security flaws one may not realize there is a weakness until that weakness has been exploited. An example would be a [http://en.wikipedia.org/wiki/Zero-day_attack] vulnerability which means no-one has seen that method of attack until it occurs.
+
Security flaws can be a weakness in the design of an application or in the procedures in using an application. Also a security flaw can be know or unknown. With known security flaws it may be possible to create procedure to mitigate those know weaknesses. With unknown security flaws one may not realize there is a weakness until that weakness has been exploited. An example would be a [http://en.wikipedia.org/wiki/Zero-day_attack|Zero-day_attack] vulnerability which means no-one has seen that method of attack until it occurs.
  
 
Security flaws can be related to:
 
Security flaws can be related to:

Revision as of 00:51, 7 April 2015

Security flaws can be a weakness in the design of an application or in the procedures in using an application. Also a security flaw can be know or unknown. With known security flaws it may be possible to create procedure to mitigate those know weaknesses. With unknown security flaws one may not realize there is a weakness until that weakness has been exploited. An example would be a [1] vulnerability which means no-one has seen that method of attack until it occurs.

Security flaws can be related to:

  • Security measures with the organization
  • Physical environment of the system
  • hardware
  • software
  • communication
  • business operations
  • administration procedures


References