Cookie Control

This site uses cookies to store information on your computer.

Some cookies on this site are essential, and the site won't work as expected without them. These cookies are set when you submit a form, login or interact with the site by doing something that goes beyond clicking on simple links.

We also use some non-essential cookies to anonymously track visitors or enhance your experience of the site. If you're not happy with this, we won't set these cookies but some nice features of the site may be unavailable.

(One cookie will be set to store your preference)
(Ticking this sets a cookie to hide this popup if you then hit close. This will not store any personal information)

About this tool

About Cookie Control

         

APT (Advanced Persistent Threat)

Mon, 09/07/2015 - 10:41 -- pottol

Introduction to APT

APT Assessment

 APT changes the approach of currently performing Security Assessment. Indeed, the way of conducting such an analysis changed over the time:

  • In '80s and '90s, it was based on VA and PT, mainly; making use of trusted methodology, like OSSTMM.
  • In '00s, when the Web 2.0 was introduced, Web Application PT should be addedd, adopting OWASP Testing Guide
  • In '10s,  APT become pervasive, also the Threat Assessment should be count in.

In order to forecast the effects of APT exploit in a company infrastructure, an assessment based solely on vulnerabilities (wheather TCP-IP, HTML, etc) residing in server systems (a few, in numbers) is not sufficient. The clients (many) are now addressed. 

In order to make countermeasures manageable, a proper threat assessment should be conducted. Here a White Paper from Gartner "Threat Assessment in the Age of the APT:

https://www.gartner.com/doc/2738617/threat-assessment-age-apt

APT Detection