Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>HP Fortify SCA has 6 analyzers: data flow, control flow, semantic, structural, configuration, and buffer. Each analyzer finds different types of vulnerabilities.</p> <p><strong>Data Flow</strong> This analyzer detects potential vulnerabilities that involve tainted data (user-controlled input) put to potentially dangerous use. The data flow analyzer uses global, inter-procedural taint propagation analysis to detect the flow of data between a source (site of user input) and a sink (dangerous function call or operation). For example, the data flow analyzer detects whether a user-controlled input string of unbounded length is being copied into a statically sized buffer, and detects whether a user controlled string is being used to construct SQL query text.</p> <p><strong>Control Flow</strong> This analyzer detects potentially dangerous sequences of operations. By analyzing control flow paths in a program, the control flow analyzer determines whether a set of operations are executed in a certain order. For example, the control flow analyzer detects time of check/time of use issues and uninitialized variables, and checks whether utilities, such as XML readers, are configured properly before being used.</p> <p><strong>Structural</strong> This detects potentially dangerous flaws in the structure or definition of the program. For example, the structural analyzer detects assignment to member variables in Java servlets, identifies the use of loggers that are not declared static final, and flags instances of dead code that will never be executed because of a predicate that is always false.</p> <p><strong>Semantic</strong> This analyzer detects potentially dangerous uses of functions and APIs at the intra-procedural level. Basically a smart GREP.</p> <p><strong>Configuration</strong> This analyzer searches for mistakes, weaknesses, and policy violations in an application's deployment configuration files.</p> <p><strong>Buffer</strong> This analyzer detects buffer overflow vulnerabilities that involve writing or reading more data than a buffer can hold.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow does Fortify software work?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USLaJmOn
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow does Fortify software work?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the very useful information. Do you know how these analyzers works internally?? I would greatly appreciate if you provide some details about this.
      singulars
      1. PO
      1. USNewbie
    2. COThere is a good, but dry, book on the subject: http://www.amazon.com/Secure-Programming-Static-Analysis-Brian/dp/0321424778
      singulars
      1. PO
      1. USLaJmOn
    3. COThere's also now a Content analyzer, although this works similarly to the configuration analyzer except searches in non-config files for issues (such as looking in HTML, JSP for XPath matches)
      singulars
      1. PO
      1. USlavamunky
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload