"... In PAGE 12: ... Table3 gives all possible security requirements on the device manager. This experiment shows that our method is able to derive ADL specifications for intrusion detection and isolation, even when we do not know how the attacks are carried out.... ..."

"... In PAGE 6: ... Implementation Schedule. Table1 summarizes the implementation schedule for FIPS 140-1. The effective date of this standard is June 30, 1994.... In PAGE 6: ... A copy of the written affirmation shall have been sent to the Director, Computer Systems Laboratory, National Institute of Standards and Technology, Gaithersburg, MD 20899. Table1 : FIPS 140-1 Implementation Schedule... In PAGE 22: ... These areas include basic design and documentation, module interfaces, authorized roles and services, physical security, software security, operating system security, key management, cryptographic algorithms, electromagnetic interference/electromagnetic compatibility (EMI/EMC), and self-testing. Table1 summarizes the security requirements in each of these areas. A cryptographic module shall be tested against the requirements of each area addressed in this section.... ..."

"... In PAGE 6: ... Implementation Schedule. Table1 summarizes the implementation schedule for FIPS 140-1. The effective date of this standard is June 30, 1994.... In PAGE 6: ... A copy of the written affirmation shall have been sent to the Director, Computer Systems Laboratory, National Institute of Standards and Technology, Gaithersburg, MD 20899. Table1 : FIPS 140-1 Implementation Schedule... In PAGE 22: ... These areas include basic design and documentation, module interfaces, authorized roles and services, physical security, software security, operating system security, key management, cryptographic algorithms, electromagnetic interference/electromagnetic compatibility (EMI/EMC), and self-testing. Table1 summarizes the security requirements in each of these areas. A cryptographic module shall be tested against the requirements of each area addressed in this section.... ..."

"... In PAGE 16: ... In this paper, we will refer only to those non- functional requirements, which deal with security. These requirements are described on Table3 , where every security focused require- ment is first associated with its aim and then briefly described. 8.... ..."

"... In PAGE 28: ...laintext secret and private keys and CSPs (i.e., tamper response). Table2 summarizes the physical security requirements, both general and embodiment-specific, for each of the four security levels. The general physical security requirements at each security level are all three distinct physical embodiments of a cryptographic module.... ..."

"... In PAGE 3: ...eadlines and the U.S. Census data are required by law to remain secret for 100 years. Table2 (cited from Ref. [14]) shows the security requirements for different kinds of information.... ..."

"... In PAGE 27: ... If the critical asset had been cheaper than the hub, the security requirement would have been simply to keep a duplicate of the asset to change it whenever it fails. The number of requirements from the security profile reused is shown in Table2 . It can be noted that the percentage of reuse was high, above all in the requirements of the information layer because it includes the requirements concerning the personal protection data, which are legally enforced in Spain.... In PAGE 37: ... Table legends Table 3 Sommerville and Sawyer apos;s top ten guidelines. Table2 . Results of the application of SIREN for security requirements ... ..."

"... In PAGE 7: ... After this period, only FIPS 140-1 validated cryptographic modules will be considered as meeting the provisions of this standard. Table2 summarizes the schedule for acquisition of FIPS 140 compliant equipment. For up to three years following June 30, 1994, equipment with cryptographic modules complying to FIPS 140, General Security Requirements for Equipment Using the Data Encryption Standard (formerly Federal Standard 1027), may be purchased in lieu of equipment with modules that comply with this standard.... In PAGE 31: ... The physical security requirements are separated into three distinct physical embodiments: single-chip modules, multiple-chip embedded modules, and multiple-chip standalone modules. Table2 summarizes the physical security requirements for the three different physical embodiments of a module for each of the four security levels. Depending on the security level of a cryptographic module, the physical security mechanisms may be designed such that unauthorized attempts at access, use or modification will either have a high probability of being detected subsequent to the attempt by leaving visible signs (i.... ..."