Èíñòðóêöèè ïî ðàáîòå ñ SQL Server 2005 ñ ïàêåòîì îáíîâëåíèÿ 1 èëè áîëåå ïîçäíåé âåðñèè SQL Server â FIPS 140-2-ñîâìåñòèìûé ðåæèì

 äàííîé ñòàòüå FIPS 140-2 èíñòðóêöèè è êàê èñïîëüçîâàòü SQL Server 2005 ñ ïàêåòîì îáíîâëåíèÿ 1 (SP1) èëè áîëåå ïîçäíåé âåðñèè SQL Server â FIPS 140-2-ñîâìåñòèìûé ðåæèì.

×òî òàêîå FIPS?

Äëÿ Federal Information Processing ñòàíäàðòà îçíà÷àåò FIPS. FIPS — ýòî ñòàíäàðò, ðàçðàáîòàííûé äâà ïðàâèòåëüñòâåííûõ òåëà. Îí NIST, Íàöèîíàëüíûì èíñòèòóòîì ñòàíäàðòîâ è òåõíîëîãèé, â ÑØÀ. Âòîðîé – CSE óñòàíîâêè áåçîïàñíîñòè ïîäêëþ÷åíèÿ, â Êàíàäå. Ñòàíäàðòû, êîòîðûå ìîãóò áûòü ðåêîìåíäóåòñÿ èëè mandated äëÿ èñïîëüçîâàíèÿ â ýêñïëóàòàöèè ãîñóäàðñòâåííûõ ÈÍÔÎÐÌÀÖÈÎÍÍÛÕ ñèñòåì Ôåäåðàëüíîé (ÑØÀ è Êàíàäû) — ýòî FIPS.

×òî òàêîå FIPS 140-2

FIPS 140-2 — ýòî îïåðàòîð "òðåáîâàíèé áåçîïàñíîñòè äëÿ êðèïòîãðàôè÷åñêèõ ìîäóëåé." Îí óêàçûâàåò àëãîðèòìû øèôðîâàíèÿ è õåøèðîâàíèÿ àëãîðèòìû ìîãóò áûòü èñïîëüçîâàíû è êàê êëþ÷è øèôðîâàíèÿ äîëæíû áûòü ñîçäàíû è óïðàâëÿòü èìè. Ýòî âîçìîæíî äëÿ íåêîòîðûõ àïïàðàòíîå îáåñïå÷åíèå è ïðîöåññû äëÿ FIPS 140-2-ñåðòèôèêàò. Èìååòñÿ òàêæå âîçìîæíîñòü äëÿ íåêîòîðûõ êàê ñîâìåñòèìûé ñ FIPS 140-2.

Ðàçëè÷èå ìåæäó, ñîâìåñòèìûì è FIPS 140-2-ñåðòèôèêàò, FIPS 140-2

SQL Server 2005 ñ ïàêåòîì îáíîâëåíèÿ 1 èëè áîëåå ïîçäíåé âåðñèè SQL Server ìîæíî íàñòðîèòü è çàïóñòèòü òàêèì îáðàçîì, ñîâìåñòèìûé ñ FIPS 140-2. ×òîáû ñäåëàòü ýòî, SQL Server 2005 ñ ïàêåòîì îáíîâëåíèÿ 1 èëè áîëåå ïîçäíåé âåðñèè SQL Server äîëæíà âûïîëíÿòüñÿ â îïåðàöèîííîé ñèñòåìå, ñåðòèôèöèðîâàííûõ FIPS 140-2, èëè ïðåäîñòàâëÿåò êðèïòîãðàôè÷åñêîãî ìîäóëÿ, êîòîðûé áûë ñåðòèôèöèðîâàí. Ðàçíèöà ìåæäó ñîâìåñòèìîñòè è ñåðòèôèêàöèè íå ÿâëÿåòñÿ íåáîëüøèì. Àëãîðèòìû ìîãóò èìåòü ñåðòèôèêàò. Îáðàòèòå âíèìàíèå, ÷òî ýòî íå ÿâëÿåòñÿ äîñòàòî÷íîé, ÷òîáû èñïîëüçîâàòü àëãîðèòì èç ñïèñêà ðàçðåøåííûõ FIPS 140-2. Ýòî íåîáõîäèìî äëÿ èñïîëüçîâàíèÿ ýêçåìïëÿð òàêîãî àëãîðèòìà, êîòîðûé áûë ñåðòèôèöèðîâàí. Ñåðòèôèêàöèè òðåáóåòñÿ òåñòèðîâàíèå è ïðîâåðêó â ëàáîðàòîðèè óòâåðæäåííûå ïðàâèòåëüñòâîì îöåíêè. Microsoft Windows Server 2003 è Microsoft Windows XP ñîäåðæèò Ðàçðåøåííûå àëãîðèòìû è ýêçåìïëÿð êàæäîãî èç íèõ áûëà îöåíêè ëàáîðàòîðèè òåñòèðîâàíèÿ è ïðàâèòåëüñòâåííûõ Ñåðòèôèöèðîâàí.

Êàêèå êîìïîíåíòû ïðèëîæåíèÿ ìîãóò áûòü FIPS 140-2 ñ?

Âñå ïðèëîæåíèÿ, âûïîëíÿþùèå øèôðîâàíèÿ è õåøèðîâàíèÿ è çàïóñêàòü ñåðòèôèöèðîâàííûå âåðñèè Microsoft Windows èìåþò âîçìîæíîñòü áûòü ñîâìåñòèìûì ñ ïîìîùüþ òîëüêî ñåðòèôèöèðîâàííûå ýêçåìïëÿðîâ óòâåðæäåííûõ àëãîðèòìû è ñîáëþäåíèå ãåíåðàöèè êëþ÷åé è òðåáîâàíèÿì óïðàâëåíèÿ êëþ÷àìè, ñ ïîìîùüþ ôóíêöèè Windows äëÿ ýòèõ èëè ñëåäîâàíèå äëÿ ãåíåðàöèè êëþ÷åé è óïðàâëåíèå òðåáîâàíèÿìè ïðèëîæåíèÿ. It should be noted that within an application places may exist where non-compliant algorithms or processes are allowed within a FIPS compliant application. For example, some internal processes that stay within the system or some external data that is to be further encrypted by a certified algorithm instance are allowed.

Does this mean that SQL Server 2005 SP1 or a later version of SQL Server is always FIPS 140-2 compliant?

Íåò,. It means that SQL Server 2005 SP1 or a later version of SQL Server can be FIPS 140-2 compliant, because it can be configured and run such that it uses only the FIPS 140-2 certified algorithm instances called by using the Windows CryptoAPI for encryption or by hashing in every instance where FIPS 140-2 compliance is required.

How can SQL Server 2005 SP1 or a later version of SQL Server be configured to be FIPS 140-2 compliant?

• Operating system requirement
  You must install SQL Server 2005 SP1 or a later version of SQL Server on a Windows Server 2003-based server or on a Windows XP-based server.
• Windows system administration requirement
  The FIPS mode must be set before SQL Server 2005 SP1 or a later version of SQL Server is started. SQL Server reads the setting at startup. Âûïîëíèòå ñëåäóþùèå äåéñòâèÿ::
  1. Log on to Windows as a Windows system administrator:
  2. çàòåì –START ::.
  3. çàòåì –control panel.
  4. çàòåì –Àäìèíèñòðèðîâàíèå.
  5. çàòåì –Ëîêàëüíàÿ ïîëèòèêà áåçîïàñíîñòè.. íàäïèñüþËîêàëüíûå ïàðàìåòðû áåçîïàñíîñòèwindow appears.
  6. Â ëåâîé îáëàñòè ùåëêíèòå ññûëêóËîêàëüíûå ïîëèòèêèè âûáåðèòå êîìàíäóÏàðàìåòðû áåçîïàñíîñòè.
  7.  ïðàâîé îáëàñòè äâàæäû ùåëêíèòå çíà÷îêÑèñòåìíàÿ êðèïòîãðàôèÿ: èñïîëüçîâàòü FIPS ñîâìåñòèìûå àëãîðèòìû äëÿ øèôðîâàíèÿ, õåøèðîâàíèÿ è ïîäïèñûâàíèÿ.
  8.  ïîÿâèâøåìñÿ äèàëîãîâîì îêíå íàæìèòå êíîïêóâêëþ÷åíè âûáåðèòå êîìàíäóÏðèìåíåíèå.
  9. çàòåì –Ok..
  10. ÇàêðûòüËîêàëüíûå ïàðàìåòðû áåçîïàñíîñòèîáîçðåâàòåëÿ..
SQL Server administrator requirement
• When the SQL Server service detects that the FIPS mode is enabled at startup, SQL Server logs the following message in the SQL Server error log:
  Service Broker transport is running in FIPS compliance mode
  Additionally, you may find the following message is logged in the Windows Event log:
  Database Mirroring transport is running in FIPS compliance mode
  You can verify that the server is running in the FIPS mode by these messages.
• For dialog security (between services), the encryption will use the FIPS-certified instance of AES if the FIPS mode is enabled. If the FIPS mode is disabled, the encryption will use RC4.
• When you configure a Service Broker endpoint in the FIPS mode, the administrator must specify "AES" for the Service Broker. If the endpoint is configured to RC4, SQL Server will generate an error. Therefore, the transport layer will not start.

How is SQL Server 2005 SP1 or a later version of SQL Server operated in FIPS 140-2 compliant mode?

• With the FIPS mode in Windows turned on, in all places where the user has no choice about whether to encrypt/hash and how it will be done, SQL Server 2005 SP1 or a later version of SQL Server will execute in compliance with FIPS 140-2. (SQL Server 2005 SP1 or a later version of SQL Server will use the CryptoAPI in Windows and will use only the certified instances of the algorithms.)
• With the FIPS mode in Windows turned on, in all places where the user has a choice of whether or not to use encryption, SQL Server 2005 SP1 or a later version of SQL Server will either allow only FIPS 140-2 compliant encryption or will not allow any encryption.
• Important information for application developers
  In all places where the developer or the user writes his or her own code for encryption or hashing, they must be instructed to use only the Windows CryptoAPI (and therefore only the certified instances) and to specify only the algorithms allowed by FIPS 140-2, specifically only Triple DES (3DES) or AES for encryption and only SHA-1 for hashing.

What is the effect of running SQL Server 2005 SP1 or a later version of SQL Server in FIPS 140-2 compliant mode?

• The use of stronger encryption may have a small effect on performance for those processes where less strong encryption is allowed when the process is not operating as FIPS 140-2 compliant.
• Selection of encryption for SSIS (UseEncryption=True) will generate an error message that the available encryption is incompatible with FIPS compliance and is not allowed. In other words, no encryption of the message process is performed.
• The use of encryption with legacy DTS is not compliant with FIPS 140-2. Note that for DTS, the FIPS mode in Windows is not checked, and it is the responsibility of the user to select no encryption to remain compliant.
• Because most SQL Server 2005 encryption and hashing processes were already FIPS 140-2 compliant, executing at full compliance (with the FIPS mode in Windows turned on) will have little or no effect on the use or performance of the product.

Where can I learn more about FIPS 140-2?

For more information about the standard and how to download it, visit the following NIST Web site: