(Please see specifications)

(Please see specifications)

Prelude

A commonly available tool for the Source Code static analysis (SCA, Static Code Analyzer) is a tool aimed to perform a parsing of the application source code in order to create a reference model on which to apply specific rules to identify problems and create a detailed report. There are a number of complete and efficient SCA tools available on the market.

Problem to be addressed

Based on our experience an ideal SCA tool should have the following additional characteristics: - multiplatform support;

- multi programming language support (with complete grammars, without “syntax holes”);

- ability to execute in stand alone mode or integrated with the most utilized development environment;

- Open Source distribution, with a strong community support;

- Security issues dedicated, with a clean separation between the analysis engine and vulnerability repository;

- Able to analyze large code bases with high performance.

Proposal

ASTRanger Project foresees the prototype development of a tool for the static analysis of source code that is going to address all of the above problems and will be able to assure that correct security rules (based on OWASP best practices) will be applied at the same time of the source code implementation. The tool will be embedded on the application developed, in such a way becoming a real Security Framework.

Milestones:

June 30, 2009 - Project Begins

July 10, 2009 – Requirements Analysis: Functional Requirements Document (FRD)

July 16, 2009 – Requirements Analysis: SAR (System Architectural Requirements)

July 20, 2009 – Identify vulnerabilities and exploitation methods.

July 24, 2009 - Defining rules set for selected vulnerabilities

July 28 2 2009 - Create thresholds for generating security alerts

Aug 3 2009 - Define parsing source code actions in response to security alerts

Aug 6 2009 - Development

Aug 18 2009 – Test and debugging

Aug 28, 2009 - Peer Review & Revisions

Aug 31, 2009 – Deliver of Prototype (Project Completion)

(Please see specifications)

(Please see specifications)

Prelude

Please find the sources and documentation at http://sourceforge.net/projects/assetmng.

The application is already production-ready. However, the functionalities below need further analysis:

  - Asset management (asset identification, valuation and risk assessment based on ISO27005); integration with opensource Security Information Management systems is currently being discussed.

  - Party management (clients, providers)

  - Contract and license management - integration with opensource tools such as OCS Inventory needs to be investigated, assetmng offering complementary functionalities.

Problems to be addressed

   - Integration of different asset valuation and risk assessment models;

   - Integration with opensource Security Information Management systems

Functionalities
1/ already implemented: managers/business analysts use the interface in order to:

 - define assets and business process and their intrinsic values;
 
 - classify these assets according to ISO27005 guidelines
 
 
 

2/ to be developed: the application calculates asset values taking into an account 

 - the intrinsic value of the asset defined in step 1;
 
 - the values of other assets depending on this asset;
 
 - the values of business processes using the asset.
 
 
 

The concept of an “asset” derived from ISO 27005

================================================

An asset can be:

- a business process or activity;

- information;

- a supporting asset such as a server or a network device.

3/ already implemented: the Legal or HR departments can use the application in order to manager parties and contracts

4/ already implemented: IT or helpdesk can use the application in order to manage licenses as well as their relationships to contracts and servers

Milestones:

July 16th, 2009 - Sources and documentation published at http://sourceforge.net/projects/assetmng

August 1st, 2009 – Identify improvements, new functionalities and integration options

Aug 10th, 2009 - Development

Aug 18th, 2009 – Test and debugging

Aug 28, 2009 - Peer Review & Revisions

Aug 31, 2009 – Deliver of Prototype (Project Completion)