Build operational security guide

Revision as of 10:37, 29 May 2009 by Deleted user (Talk | contribs)

Jump to: navigation, search

[ australian name puppy shepherd ] [ south african boy names ] [ toshiba notebooks australia ] [ grand theft auto vice city x box walkthrough ] [ 3 australian formula ] [ moscow asia travel mart ] links african american music during the harlem renaissance [ 2 4890508.stm africa go hi rss ] [ african dance fanga video ] australia bank fee loan personal [ walt disney fantasia 2000 ] [ australia england cricket trophy the ] [ kalulu south africa ] [ south african food online ] [ privacy laws in australia ] [ travel and tourism south africa ] http [ concours auto detailing ] [ auto login to windows ] [ east african breweries ltd ] [ pan macmillan south africa ] [ australian miniature bulldog puppies ] [ australia tourist visa uk ] antivirus online scanning [ dynasties in asia ] [ symantec antivirus download ] [ hairy asian movies ] [ robert kennedy speech south africa ] [ african court of human peoples right ] [ techsmith camtasia studio v2.1.2 ] [ african instrumentals ] [ daimler chrysler south africa ] [ african gray ] [ asian skirts ] [ womens golf australia ] [ euthanasia views ] [ antivirus software downloadable ] [ australia genealogy in marketing network report ] [ south african association of freight forwarders ] [ australia job finder ] [ building automation systems compatible with johnson controls ] [ norton antivirus 2006 does not support the repair feature ] [ netball australia home ] map [ symantec antivirus corporate ] download autoroute 2005 symantec antivirus corporate edition 10 x [ auto decal side graphics ] [ african wear for child ]



  • Provide stakeholder with documentation on operational security measures that can better secure the product.
  • Provide documentation for the use of security functionality within the product.


  • Implementer


  • Once per iteration.

In the course of conception, elaboration, and evaluation, there will generally be many items identified that should be communicated to one or more roles at deployment. This information should all be collected in a role-driven implementation guide that addresses security concerns.

Document pre-install configuration requirements

Begin by documenting the environmental requirements that must be satisfied before the system is installed. See the task on operational environment assumptions for more detail.

Document application activity

Document any security-relevant use of resources, including network ports, files on the file system, registry resources, database resources etc. See the activity on Resource identification for more detail.

Document the security architecture

Document the threat profile assumed in design and the high-level security functionality of the system as relevant to the user - including authentication mechanisms, default policies for authentication and other functions, and any security protocols that are mandatory or optional. For protocols used, document the scope of their protection.

Document security configuration mechanisms

List, and explain all security configuration options present in the system, and make note of their default and recommended settings. Be explicit about how they work, referencing any technologies utilized.

Document significant risks and known compensating controls

Any known security risks that the customer may find reasonable should be documented, along with recommended compensating controls, such as recommended third party software that can mitigate the issue, firewall configurations, or intrusion detection signatures.