27.10.2016 09:57:23

This article discusses the technical design stage related to one of the stages of the system life cycle information security(NIB) - the "design" stage, which, in accordance with domestic standard GOST 34.601-90 immediately follows the development of the Terms of Reference for an information security system.

1. Development of technical project documentation for NIB

The life cycle of an information security system (hereinafter - SIS) in general consists of the following stages:

• analysis of requirements for ISS;
• design;
• implementation;
• implementation;
• exploitation.

This article discusses the stage of the technical project related to the "design" stage and, in accordance with the domestic standard GOST 34.601-90, immediately follows the development of the Terms of Reference for the information security system.

1.1. Why develop documentation for NIB at all?

The answer to this question should be considered in two planes: in the plane of the owner of information resources (for the protection of which the ISS is created) and in the plane of the direct developer of the ISS.

For the owner of information resources, it is important to get the result in the form of a functioning information security system that reduces the risks of compromising restricted access information in the organization. The technical project in this case serves to develop the fundamental foundations of the future system, namely, it includes a description of how the ISS will be built and function, what measures and means will ensure the protection of information, what are the possibilities for developing and improving the system. Upon completion of the development of a technical project for an information security system, the Customer receives a comprehensive set of documentation for the NIS, which describes all the technical nuances of the future system.

For the direct executor at the stage of the technical project, it is necessary to lay down the most appropriate architecture of the NIS, as well as to make right choice measures and means of protecting information in the organization. It is also important to ensure that the characteristics and properties of the system comply with the terms of reference, or to justify, with the participation and consent of the Customer, the adjustment of the requirements specified in the TOR in order to increase the efficiency of the system being created.

Thus, as a result of the development of technical project documentation, the Customer will have answers to the following questions:

• what is the general architecture of the NIB;
• what measures and means will be used to implement the requirements for information protection;
• how the NIS will function;
• what changes in the organization, necessary to increase the level of information security, will follow as a result of the introduction of the ISS;
• whether the requirements of the Customer (business requirements) and the requirements of regulatory legal acts in the field of information security will be taken into account in the development and implementation of the ISS and, if so, how.

The contractor in the process of developing the technical project documentation will receive the following results:

• the basis for the transition to the next stages of building the NIS, namely the stages of working documentation and implementation;
• understanding of the architecture, technologies and tools used, the order of building the system;
• how the requirements of the Customer (business requirements) and regulatory documents in the field of information security for the system are implemented.

1.2. Overview of approaches to the development of technical project documentation

The development of a technical project for an information security system is most often carried out on the basis of relevant standards and guidance documents. And for public institutions their use is mandatory, and for commercial purposes it is recommended. On practice commercial organizations also use state standards when developing technical project documentation for the following reasons:

• repeatedly proven approach to the creation of information systems;
• thoughtful structure and content of documents;
• a set of documents sufficient for the development and description of almost any system.

For the development of documentation for the stage of the technical project (TP) on the NIB, state standards and guidance documents of the 34 series are used:

• GOST 34.201-89 "Types, completeness and designation of documents when creating automated systems." This standard specifies:
  • types and names of documents of the TP stage;
  • completeness of documentation;
  • accepted designations of documents;
  • rules for the designation of NIBs and their parts.
• GOST 34.003-90 "Terms and definitions";
• GOST 34.601-90 “Automated systems. Stages of creation. The standard specifies:
  • list of stages of work carried out at the TP stage;
  • detailed description works carried out at the TP stage;
  • list of organizations participating in the creation of the NIS;
• RD 50-34.698-90 “Automated systems. Requirements for the content of documents. This guidance document specifies the requirements for the content of the TA stage documents.

It is important to understand that according to the 34 series standards, a technical project is a stage in the creation of a system, and not just a set of documents. This stage in practice is often combined with the preliminary design stage, which serves to develop several preliminary solutions and substantiate the most suitable one. Such a combination is allowed by the standard, but it must be borne in mind that this does not negate the need to achieve the objectives of the preliminary design stage.

Most often, the draft design stage is developed when the requirements of the technical specifications for the system can be implemented in several fundamentally different ways, and also if there are no unambiguously preferred methods among these methods.

However, it should be noted that the above standards are too general and mainly implement a design and general structural function. To develop the substantive part of the documents of the technical design stage, designers use information from the following sources:

Current regulatory documents (NLA) that regulate the requirements for the protection of this or that information of limited access. These RLAs present the requirements for measures to protect information in information systems, describe the nuances of the implementation of these measures and additional strengthening measures. Among the current NPAs, the following can be distinguished:

• order of the FSTEC of Russia dated February 18, 2013 No. 21 “On approval of the composition and content of organizational and technical measures to ensure the security of personal data when they are processed in personal data information systems”;
• order of the FSTEC of Russia dated February 11, 2013 No. 17 "On approval of requirements for the protection of information that is not a state secret contained in state information systems"
• order of the FSTEC of Russia dated March 14, 2014 No. 31 "On approval of requirements for ensuring the protection of information in automated control systems for production and technological processes at critically important facilities, potentially dangerous facilities, as well as facilities that pose an increased danger to human life and health and to the natural environment;
• methodological document "Information protection measures in state information systems", approved by the FSTEC of Russia on February 11, 2014

The requirements for the protection of information of restricted access and the lists of protective measures vary for IS of different levels/classes of security. If the information in the organization does not belong to the protected in accordance with federal laws RF (for example, an official secret), then the owner of this information can use the approaches proposed in these legal acts to build a corporate ISS.

Russian and foreign standards, describing various approaches to the ways of implementing the stages of the life cycle of building an ISS, including the stages of a technical project:

• a series of state standards GOST R ISO/IEC 2700X, identical to the international standards ISO/IEC 2700X. These standards describe the PDCA (Plan, Do, Check, Act) process approach to the implementation of the information security management system life cycle, which is an integral part of the ISS;
• NIST SP 800-64 is a US National Institute of Standards and Technology standard that describes life cycle development of information systems;
• NIST SP 800-37 is a US National Institute of Standards and Technology standard that provides guidance on integrating risk management into the information systems development life cycle.

Manufacturer's operational documentation for information security and aids. These documents contain comprehensive technical information about the tools used in the construction of the ISS, including those that are not directly related to the implementation of IS measures, for example, servers, data storage systems, virtualization tools, and others. The general set of such documents for different manufacturers is different and depends, among other things, on the execution of a particular tool (hardware/software). Below is a standard set of operational documentation for information security tools used to develop documents for the technical project stage:

• general description (datasheet);
• administrator's guide (may include local and centralized management guide);
• user guide;
• quick installation and deployment guide (for hardware GIS);
• operator's manual;
• virtual infrastructure deployment guide (for software GIS);

General information about available NIS architectures, best practics in terms of building ISS, guidance on security and integration of information security equipment with each other, information about problems in the interaction of certain information security facilities. Examples of such information may include the following documents:

• information security system architecture guides, for example: Defense-in-Depth, Cisco SAFE, Check Point SDP and others;
• information security best practices, such as those available at these links (https://www.sans.org/reading-room/whitepapers/bestprac/ , http://csrc.nist.gov/publications/nistpubs/800-14 /800-14.pdf). These documents are most often presented on English language, however, any Russian manufacturer SZI and upon request they can be provided;
• safety guides for IPS and operating environments. An example is the "Security" section on the official Microsoft portal (https://technet.microsoft.com/ru-ru/library/dd637672.aspx).

1.3. Development of a technical design for the NIB in accordance with GOST 34

The development of documents for the technical project stage at the NIS is most often carried out by integrators of these services and is implemented mainly in accordance with the following plan:

Determination of the list of documents to be developed - this information is indicated in the terms of reference for the NIS. In some cases, the developer of documents, in agreement with the Customer, can expand or reduce this list, if the possibility of this is provided for in the TOR;

Development of document templates for the TP stage - the structure is used in accordance with RD 50-34.698-90 and GOST 2.106 (for some documents), execution in accordance with GOST 2.105-95;

Development of the substantive part of the documents. Requirements for the system are set in the terms of reference for the NIB. In accordance with these requirements, a list of protective technical and organizational measures necessary for implementation in the system is determined. Protection measures can be defined in the relevant regulatory legal acts (depending on the type of information being protected), corporate standards and information security policies, as well as based on the presence of current security threats identified during the development of the organization's threat model. Based on the list of protection measures, the ISS developer selects the appropriate information protection tools and develops the functional structure of the information security system (subsystems, components). Further in the technical design documents it is described practical implementation protection measures based on the selected GIS or organizational measures in the infrastructure of the organization.

Coordination of the developed documentation and the solutions presented in it with the Customer of the system.

When developing technical project documentation, most often it is not required to develop a complete list of documents specified in GOST 34.201-89, since this standard is obsolete and some of the documents do not take into account the development trends and technologies of modern information systems. The minimum set of documents required to describe an information security system is as follows:

• statement of the technical project;
• explanatory note to technical project;
• scheme functional structure;
• structural diagram of the complex technical means;
• organizational chart;
• list of purchased items.

At the request of the Customer or if the NIS is a complex multicomponent system, the following documents can be additionally developed:

• automation scheme;
• description of automated functions;
• description information support systems;
• description of the complex of technical means;
• description software;
• description of the organizational structure.

It should be noted that GOST 34.201-89 allows for the expansion of the range of documents at the TP stage, however, in practice, these documents are more than enough.

Technical design sheet

Designation: TP.

This document is intended to describe the list of documents developed at the stage of the technical project. The number of pages of each of the developed documents is also indicated.

Explanatory note to the technical project

Designation: P2.

This document is the main one for the TP stage and includes a description of the ISS architecture, technical and organizational measures, ISS functions, software and hardware complexes, and others. According to the standard, it consists of four main sections:

• general provisions;
• description of the activity process;
• main technical solutions;
• measures to prepare the automation object for putting the system into operation.

Functional structure diagram

Designation: C2.

This document describes the logical structure of the NIS, namely:

• logical subsystems and components included in the NIS;
• functions implemented by means of subsystems and components;
• information links between logical elements of the NIS and types of messages in the exchange.

Structural diagram of a complex of technical means

Designation: C1.

This document includes a description of the following elements of the NIS:

• technical means as part of the logical subsystems and components of the NIS;
• communication channels and exchange between technical means with indication of transport protocols.

Organization chart

Designation: C0.

This document describes organizational structure organizations in terms of NIS management, namely:

• subdivisions and responsible persons of the organization involved in the functioning of the ISS;
• functions performed and communications between departments and responsible persons.

List of purchased products

Designation: VP.

This document includes a list of all software and hardware, as well as licenses used in the creation of the NIS. Developed in accordance with GOST 2.106.

Note. It is also worth noting here that the governing document RD 50-34.698-90 allows the addition of any document of the TP stage (inclusion of sections and information other than those proposed), the merging of sections, as well as the exclusion of some individual sections. Decisions about this are made by the developer of documents of the TP stage and are based on the features of the created NIS.

1.4. Documentation development rules

• structural conformity state standards;
• strict compliance with the requirements of the technical specifications for the system;
• application of document templates (application of uniform styles, markup, fields, etc.);
• individual approach and simultaneous use of existing developments when filling out sections of documents.

Explanatory note to the technical project:

• the development of the document is carried out in the Microsoft Word environment, after the completion of the development it is recommended to convert the document to PDF format for convenience;
• terms and abbreviations should be the same within all sections of the document;
• it is recommended to avoid explicit repetitions and unnecessary increase in the volume of the document;
• technical solutions should be described in as much detail as possible, indicating:
  • architecture and technologies used;
  • locations of software and hardware in the infrastructure of the organization;
  • used information security tools with a description of their characteristics, implemented functions, certification information;
  • basic settings of information security tools in terms of protection mechanisms, addressing, routing, interaction with related systems and tools, and other things;
  • controls, methods of access to them and their installation locations;
  • schemes (structural, functional, organizational):
    • develop diagrams in the Microsoft Visio environment;
    • after development, insert diagrams into a document using the Paste Special dialog in EMF format (Windows metafile);
    • develop separate schemes for the system, subsystems and components of subsystems;
    • make the design of schemes the same type, using the same elements, abbreviations, icons, text styles, and so on.

1.5. Resources to help you develop documentation

A huge amount of information is posted on the Internet, which, to one degree or another, can help in the development of technical project documentation. The main resources are presented in the table below.

Table. Resources for technical design NIB

1.6. Examples of documents of the stage of the technical project

To understand the requirements for the content of the documentation of the TP stage, examples of filling out the main documents (document sections) are presented below.

1.6.1. Explanatory note to the technical project

The explanatory note is a fairly voluminous document, so here is an example of the content of the section "Basic technical solutions" in terms of one of the ISS subsystems - the security analysis subsystem.

NIS security analysis subsystem

Structure and composition of the subsystem

The security analysis subsystem (SAS) is designed to systematically monitor the security status of automated workstations (AWPs) of personnel and organization servers. The basis of the PAZ is the software tool "Test" produced by the company LLC "Information Security". IPS Test is certified by the FSTEC of Russia for compliance with the technical specifications (TU) for information security and for the 4th level of control of the absence of undeclared capabilities.

The composition of the PAZ includes the following components:

• Test Server management server;
• test console management console.

The description of the subsystem components is presented in the table below.

Table. PAZ components

Feature provision

PAZ provides the following functions:

• implementation of proactive protection of workstations and servers of the organization by monitoring the state of information security;
• automation of compliance control processes domestic politicians and certain safety standards;
• reducing the cost of auditing and security control, preparation of status reports;
• automation of resource inventory, vulnerability management, security policy compliance and change control processes.

Solution for a complex of hardware and software tools

The list of software and hardware used by the ESD is given in the table below.

Table. PAZ software and hardware

PAZ control server

Technical means

The physical server used as the SIS management server must meet the technical requirements for the software and OS installed on it, given in the table below.

Table. Requirements for the OS and software of the PAZ management server

Software

Management Server OS

Windows 2008 R2 OS is installed on the management server in the usual way from a bootable distribution.

The OS of the management server is managed both locally from the console and via the RDP protocol.

Management server DBMS

The installation of the Microsoft SQL Server 2008 R2 database is carried out under an account with local administrator rights using the standard installation wizard from the distribution package supplied by the product developer.

Test Server software

The Test Server software is installed on the management server using the standard installation wizard.

The initial configuration and subsequent management of the Test Server software in normal mode is carried out using the Test Console management console installed on the IS administrator's workstation.

IS administrator workstation

Technical means

As a platform, an existing workstation of an employee of the organizational unit responsible for providing information security is used, running an OS of the Microsoft Windows family.

The technical means of the IS administrator's workstation must have the following characteristics of the hardware configuration (recommended at least):

• CPU 2 GHz;
• RAM 4 GB;
• HDD 80 GB.

Software

Test Console Software

The IS administrator's workstation, on which the Test Console software is being installed, must operate under one of the following operating systems:

• Microsoft Windows 7, 32- and 64-bit;
• Microsoft Windows 8/8.1, 32- and 64-bit.

In addition, for the correct operation of the Test Console management console software, the IS administrator's workstation must have Microsoft .NET Framework version 3.5 SP1 or higher installed, and the security settings of the OS used must allow access to the Test Server.

Installation of the Test Console software on the PAZ administrator's workstation is carried out using the standard Test Server software installation wizard with the option to install the Test Console management console and other default settings.

Interaction with related systems

For PAZ, adjacent are:

• means of the firewall subsystem;
• directory services Active Directory;
• Workstation and servers of the organization.

To ensure network interaction with adjacent systems and directly between the ESD components themselves, the passage of the necessary network traffic must be organized.

To provide the ability to receive updates of the knowledge base and modules of the Test software for the Test Server scanner, it is necessary to provide access to the update.com web server of Information Security LLC update.com on port 443/tcp.

When scanning in the PenTest mode, the interaction between the Test Server scanner and the workstation and the organization's servers is carried out via the IP protocol. When scanning in Audit and Compliance mode, the remote control protocols WMI, RPC, etc. are used. To scan nodes on devices with firewall functions, you must allow connections from the Test Server to the scanned nodes via the IP protocol. Accordingly, for the Test Server, it is necessary to provide access to the network ports of the scanned nodes using the appropriate remote control protocols.

Since PAZ, when scanning in Audit and Compliance modes, uses remote control protocols for analysis, the scanning tools of the Test software must be authenticated and authorized on the scanned node. In PAZ, to scan nodes in the Audit and Compliance modes in each of the types of nodes (workstation, server, application systems, DBMS, etc.) Accounts with administrative privileges.

All registered information security events are stored in the Microsoft SQL DBMS. These events can be sent via special connectors to the IS event monitoring subsystem.

Operation and maintenance of PAZ

Subsystem Users

The operation and maintenance of PAZ tools is carried out by employees of the organization with the functional role of "IS administrator".

An IS administrator is a specialist whose tasks include:

• defining parameters for scanning organization nodes;
• setting up and launching scanning tasks;
• analysis of scan results for vulnerabilities, configuration errors or non-compliances in information systems technical standards;
• control of elimination of vulnerabilities;
• formation of standards and requirements that apply to ensuring the security of workstations and servers of the organization.

System operating modes

Regular mode of operation

In normal operation, the PAZ operates 24 hours a day, 7 days a week.

In normal operation, the IS administrator performs:

• scheduled and unscheduled scanning of nodes;
• report generation;
• updating knowledge bases and modules of Test software.

Emergency operation

In the event of a malfunction of the PAZ means, the functioning of the subsystem is disrupted. Violation of the operability of PAZ means does not affect the functioning of the workstation and servers of the organization.

1.6.2. Functional structure diagram

Functional diagrams can be developed for the entire NIS or for a part of it, such as a subsystem or component.

An example of a general functional diagram The NIB is shown in the figure below.

1.6.3. Structural diagram of a complex of technical means

A block diagram of a complex of technical means can be developed both for the entire NIS and for its parts - subsystems and components. The expediency of developing schemes for parts of the NIS is determined by the scale of the system and the required detail.

Example block diagram of the complex of technical means of the NIS is shown in the figure below.

As a rule, the Explanatory Note is the most complex software document, sometimes causing a lot of controversy and discussion around its content. Why does this happen?

Appointment of an explanatory note

We have already said that in software development this is one of the important stages. It should contain a description of your system, taking into account the selected technologies, as required by GOST 34. And the document Explanatory note to the technical project, or, in short, PZ, is one of the main documents this stage. And, I must say, most often it is the Explanatory Note that is the most complex document on software, sometimes causing a lot of controversy and discussion around its content.

Composition of a typical explanatory note

The explanatory note to the technical project includes such sections as:

– Introduction. This section contains the full name of the system and the topic of development, as well as a list of documents that served as the basis for the work on the project.

– Purpose and scope. It describes the goals and objectives that will be solved with the help of the system, as well as the scope of its use.

– Specifications. This section is usually divided into subsections, which describe: setting the task of creating a program; used mathematical apparatus; software operation algorithm; structure of input and output data; composition of hardware and software. It is also necessary to provide calculations and analysis results to justify the choice of exactly those decisions that are mentioned in the document.

– Expected technical economic indicators . The section assumes an economic justification for the development, taking into account its technical indicators.

– Sources used in development. A section is a list of documents, articles and publications that have been referenced in the text.

Standards for explanatory note

The composition of the sections is determined by GOST 19.404, however, the standard allows these sections to be combined, if necessary, and also to add new ones. In the case of using GOST series 34, a document should be developed in accordance with RD 50-34.698. However, the document must remain within the requirements common standards, such as, for example, GOST 19.105.

The cost of developing an explanatory note

How about with least cost create a program document that is most useful for your project, which:

- on the one hand, clearly and intelligibly presents all the necessary (and sometimes boring) information, including complex technical details;

GOST 19.404-79

Group T55

INTERSTATE STANDARD

Unified system of program documentation

EXPLANATORY NOTE

Requirements for content and design

Unified system for program documentation. Explanatory note. Requirements for contents and form of presentation

Introduction date 1981-01-01

Decree State Committee CCSR according to the standards of December 11, 1979 N 4753, the date of introduction is set on 01.01.81

REPUBLICATION. January 2010


This standard establishes the requirements for the content and design of the program document "Explanatory Note", defined by GOST 19.101-77, which is part of the documents at the stages of developing the draft and technical designs of the program.

1. GENERAL PROVISIONS

1. GENERAL PROVISIONS

1.1. The structure and design of the document are established in accordance with GOST 19.105-78.

Compilation of the information part (summary and content) is optional.

1.2. The explanatory note should contain the following sections:

introduction;

Purpose and scope;

specifications;

expected technical and economic indicators;

sources used in development.

Depending on the features of the document, individual sections (subsections) may be combined, as well as new sections (subsections) may be introduced.

2.1. In the "Introduction" section indicate the name of the program and (or) symbol development topics, as well as documents on the basis of which development is carried out, indicating the organization and date of approval.

2.2. In the section "Purpose and scope" indicate the purpose of the program, brief description scope of the program.

2.3. The "Specifications" section should contain the following subsections:

setting a task for the development of a program, a description of the applied mathematical methods and, if necessary, a description of the assumptions and restrictions associated with the chosen mathematical apparatus;

description of the algorithm and (or) the functioning of the program with the rationale for choosing the scheme of the algorithm for solving the problem, possible interactions of the program with other programs;

description and justification of the choice of method for organizing input and output data;

description and justification of the choice of the composition of hardware and software based on the calculations and (or) analyzes, distribution of data carriers used by the program.

2.4. In the "Expected technical and economic indicators" section, indicate the technical and economic indicators that justify the advantage of the chosen technical solution option, as well as, if necessary, the expected operational indicators.

2.5. In the section "Sources used in the development" indicate a list of scientific and technical publications, regulatory documents and other scientific and technical materials that are referenced in the main text.

2.6. The annex to the document may include tables, justifications, methods, calculations and other documents used in the development.



Electronic text of the document
prepared by CJSC "Kodeks" and checked against:
official publication
Unified system of program documentation:
Sat. GOSTs. -
M.: Standartinform, 2010

Ministry economic development and trade Russian Federation

from 01.01.74

This standard establishes requirements for the implementation of a technical design for products in all industries.

1. GENERAL PROVISIONS

2. REQUIREMENTS FOR THE IMPLEMENTATION OF DOCUMENTS

APPENDIX

LIST OF WORKS CARRIED OUT DURING THE DEVELOPMENT OF THE TECHNICAL DESIGN

In the general case, when developing a technical project, the following work is carried out: a) development of design solutions for the product and its main components; b) performing the necessary calculations, including those confirming the technical and economic indicators established by the terms of reference; c) performing completion of the necessary circuit diagrams, connection diagrams, etc.; d) development and justification of technical solutions that provide reliability indicators established by the terms of reference and previous stages of development (if these stages were developed); e) analysis of the design of the product for manufacturability, taking into account the feedback from industrial manufacturers in terms of ensuring manufacturability in the conditions of this particular production, including the use of equipment available at the enterprise, as well as taking into account in this project the requirements of regulatory and technical documentation in force at the enterprise - manufacturer; identification of new equipment necessary for the production of products (justification of development or acquisition); development of metrological support (selection of methods and means of measurement); f) production and testing of material layouts and (or) development and analysis of electronic layouts”; g) assessment of the product in relation to its compliance with the requirements of the economy, technical aesthetics; h) assessment of the possibility of transportation, storage, and installation of the product at the place of its use; i) assessment of the operational data of the product (interchangeability, ease of maintenance, maintainability, resistance to environmental influences, the ability to quickly eliminate failures, quality control of the product, availability of control tools technical condition etc.); j) finalization of applications for the development and manufacture of new products (including measuring instruments) and materials used in the product under development; k) taking measures to ensure the level of standardization and unification of the product specified in the terms of reference; l) checking the product for patent purity and competitiveness, filing applications for inventions; m) identification of the range of purchased products, coordination of the use of purchased products; o) coordination of overall, installation and connecting dimensions with the customer or the main consumer; o) assessment of the technical level and quality of the product; p) development of drawings of assembly units and parts, if this is caused by the need to speed up the issuance of a task for the development of specialized equipment for their manufacture; c) verification of the compliance of decisions made with the requirements of safety and industrial sanitation; development and working documentation, in addition and (or) clarification of the work provided for by the terms of reference, technical proposal and draft design; additionally, Rev. No. 4) . t) preparation of proposals for the use of software and information support for automated systems in the development of working design documentation. (Introduced additionally, Amendment No. 5).