Channels ▼


Application Testing Nirvana Demands Continuous Concurrency

WhiteHat Security recently released Sentinel Source, a Static Application Security Testing (SAST) solution built for "continuous concurrent" assessment of source code development. The product tracks vulnerabilities in real-time to assess sites and web apps in both production and pre-production.

The "Problem" with Internet Growth

WhiteHat suggests that the "problem" (or "issue" at the very least) with rapid growth across the Web is that companies quickly add more functionality to online applications and unwittingly create more attack surfaces for hackers. Consequently, developers could now carry increasingly greater responsibility to protect an organization from data loss.

Sentinel Source tests web applications during development, returning code remediation data to address security issues. Code assessments may be queried as soon as new pieces of code are uploaded and on-premise scanning is designed to preserve the integrity of intellectual property by performing all assessments without the compiled source code leaving internal networks.

This is a SaaS-based solution that reports via a dashboard with what WhiteHat confirms is no false-positives, as all code assessments are verified through the firm's Threat Research Center for exploitability.

"Recent events have shown web applications are the new front-line of businesses and that developers now play a key role in not only growing the business, but protecting it as well," said Jerry Hoff, vice president, static code analysis division, WhiteHat Security.

Sentinel Source's proprietary scanning engine identifies code vulnerabilities before Agile developers have moved past them, preventing (in theory) downstream flaws that leave an organization open for attack. All vulnerability information is then available through WhiteHat Sentinel's web UI for remediation.

Sentinel Source includes Sentinel Baseline Edition (BE) to ensure all applications continue to be assessed after going live.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.