Focused On Your Success


The All.Net Security Database


Generated Fri Jun 27 09:58:50 PDT 2003 by fc@red.a.net

Cause/Mechanism:
  • Threat Profiles
  • Attack Methods
  • Defense Methods
    Process:
  • Prevention
  • Detection
  • Reaction
    Impact:
  • Integrity
  • Availability
  • Confidential
  • Use Control
  • Other:
  • Risk Management
  • Database Description

    Domain:
  • Physical
  • Informational
  • Systemic
    Sophistication:
  • Theoretical
  • Demonstrated
  • Widespread
  • Perspectives:
  • Management
  • Policy
  • Standards
  • Procedures
  • Documentation
  • Audit
  • Testing
  • Technical Safeguards
  • Personnel
  • Incident Handling
  • Legal
  • Physical
  • Awareness
  • Training
  • Education
  • Organization
  • Brekne's Mechanistic:
  • Input
  • Output
  • Storage
  • Processing
  • Transmission
  • Brekne's Causal:
  • Accidental
  • Malicious
  • Brekne's Method:
  • Leakage
  • Masquerade
  • Denial
  • Corruption
  • Usage
  • Mental

  • Attack89:

    Name:race conditions

    Complexity: Race conditions are not easy to detect. In general, they require at least NP-complete time and space and may require factorial time in some cases. Some automated analysis tools have been implemented to detect certain classes of race conditions in source code and have shown promise.
    fc@red.a.net

    Related Database Material

    [TBVAccidental - Relates to Accidental]
    [TBVDenial - Relates to Denial]
    [PDRIntegrity - Relates to Integrity]
    [PDRUse - Relates to Use]
    [PDRDemonstrated - Relates to Demonstrated]
    [PLSSystemic - Relates to Systemic]
    [Threat1 - insiders]
    [Threat4 - consultants]
    [Threat10 - hackers]
    [Threat11 - crackers]
    [Threat13 - cyber-gangs]
    [Threat14 - tiger teams]
    [Threat20 - crackers for hire]
    [Threat26 - foreign agents and spies]
    [Threat28 - government agencies]
    [Threat30 - economic rivals]
    [Threat31 - nation states]
    [Threat32 - global coalitions]
    [Threat33 - military organizations]
    [Threat35 - information warriors]
    [Defense131 - adversary principle (GASSP)]
    [Defense30 - audit analysis]
    [Defense35 - awareness of implications]
    [Defense91 - conservative resource allocation]
    [Defense13 - detection before failure]
    [Defense87 - disable unsafe features]
    [Defense21 - fault isolation]
    [Defense89 - integrity checking]
    [Defense10 - isolated sub-file-system areas]
    [Defense53 - known-attack scanning]
    [Defense37 - least privilege]
    [Defense51 - secure design]
    [Defense1 - strong change control]
    [Defense52 - testing]