hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
6031d135d1516828f3365333800112ac | 104 163 | 1 Scope | The present document is a transposition of ITU-T Technical Report QSTR.FTT [i.1] without modifications. |
6031d135d1516828f3365333800112ac | 104 163 | 2 References | |
6031d135d1516828f3365333800112ac | 104 163 | 2.1 Normative references | Normative references are not applicable in the present document. |
6031d135d1516828f3365333800112ac | 104 163 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
6031d135d1516828f3365333800112ac | 104 163 | 3 Definition of terms, symbols and abbreviations | |
6031d135d1516828f3365333800112ac | 104 163 | 3.1 Terms | For the purposes of the present document, the terms given in ITU-T Technical Report QSTR.FTT [i.1] apply. |
6031d135d1516828f3365333800112ac | 104 163 | 3.2 Symbols | Void. |
6031d135d1516828f3365333800112ac | 104 163 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ITU-T Technical Report QSTR.FTT [i.1] apply. |
6031d135d1516828f3365333800112ac | 104 163 | 4 Endorsement notice | All elements of ITU-T Technical Report QSTR.FTT [i.1] apply. ITU-T Technical Report QSTR.FTT [i.1] is contained in archive tr_104163v010101p0.zip which accompanies the present document. ETSI ETSI TR 104 163 V1.1.1 (2025-12) 6 History Version Date Status V1.1.1 December 2025 Publication |
72622361e0acd534ede2dd91705013a0 | 104 165 | 1 Scope | The present document is a transposition of ITU-T Technical Report QSTR-UCFTBS [i.1] without modifications. |
72622361e0acd534ede2dd91705013a0 | 104 165 | 2 References | |
72622361e0acd534ede2dd91705013a0 | 104 165 | 2.1 Normative references | Normative references are not applicable in the present document. |
72622361e0acd534ede2dd91705013a0 | 104 165 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
72622361e0acd534ede2dd91705013a0 | 104 165 | 3 Definition of terms, symbols and abbreviations | |
72622361e0acd534ede2dd91705013a0 | 104 165 | 3.1 Terms | For the purposes of the present document, the terms given in ITU-T Technical Report QSTR-UCFTBS [i.1] apply. |
72622361e0acd534ede2dd91705013a0 | 104 165 | 3.2 Symbols | Void. |
72622361e0acd534ede2dd91705013a0 | 104 165 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ITU-T Technical Report QSTR-UCFTBS [i.1] apply. |
72622361e0acd534ede2dd91705013a0 | 104 165 | 4 Endorsement notice | All elements of ITU-T Technical Report QSTR-UCFTBS [i.1] apply. ITU-T Technical Report QSTR-UCFTBS [i.1] is contained in archive tr_104165v010101p0.zip which accompanies the present document. ETSI ETSI TR 104 165 V1.1.1 (2025-12) 6 History Version Date Status V1.1.1 December 2025 Publication |
68edb6306c77763c51270d9f83cb79a7 | 104 162 | 1 Scope | The present document is a transposition of Recommendation ITU-T Q.4078 [1] without modifications. |
68edb6306c77763c51270d9f83cb79a7 | 104 162 | 2 References | |
68edb6306c77763c51270d9f83cb79a7 | 104 162 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
68edb6306c77763c51270d9f83cb79a7 | 104 162 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
68edb6306c77763c51270d9f83cb79a7 | 104 162 | 3 Definition of terms, symbols and abbreviations | |
68edb6306c77763c51270d9f83cb79a7 | 104 162 | 3.1 Terms | For the purposes of the present document, the terms given in Recommendation ITU-T Q.4078 [1] apply. |
68edb6306c77763c51270d9f83cb79a7 | 104 162 | 3.2 Symbols | Void. |
68edb6306c77763c51270d9f83cb79a7 | 104 162 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in Recommendation ITU-T Q.4078 [1] apply. ETSI ETSI TS 104 162 V1.1.1 (2025-12) 6 |
68edb6306c77763c51270d9f83cb79a7 | 104 162 | 4 Endorsement notice | All elements of Recommendation ITU-T Q.4078 [1] apply. Recommendation ITU-T Q.4078 [1] is contained in archive ts_104162v010101p0.zip which accompanies the present document. ETSI ETSI TS 104 162 V1.1.1 (2025-12) 7 History Version Date Status V1.1.1 December 2025 Publication |
13063999760325619f5f8127992828ea | 104 159 | 1 Scope | The present document provides an understanding of the harm from Generative AI, along with presenting the different ways to prevent that harm. This includes but is not limited to malicious code generation, deepfakes, spam messages, disinformation, etc. The areas also covered are the issues of AI hallucinations, loss of ... |
13063999760325619f5f8127992828ea | 104 159 | 2 References | |
13063999760325619f5f8127992828ea | 104 159 | 2.1 Normative references | Normative references are not applicable in the present document. |
13063999760325619f5f8127992828ea | 104 159 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
13063999760325619f5f8127992828ea | 104 159 | 3 Definition of terms, symbols and abbreviations | |
13063999760325619f5f8127992828ea | 104 159 | 3.1 Terms | For the purposes of the present document, the following terms apply: agentic AI: small, specialized pieces of software that can make decisions and operate cooperatively or independently to achieve system objectives NOTE: Agentic AI refers to AI systems composed of agents that can behave and interact autonomously to ach... |
13063999760325619f5f8127992828ea | 104 159 | 3.2 Symbols | Void. |
13063999760325619f5f8127992828ea | 104 159 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AI Artificial Intelligence AB Assembly Bill C2PA Coalition for Content Provenance and Authenticity CAIA Colorado Artificial Intelligence Act CNIL Commission Nationale de l'Informatique et des Libertés CSAM Child Sexual Abuse Material DKIM Doma... |
13063999760325619f5f8127992828ea | 104 159 | 4 Introduction | |
13063999760325619f5f8127992828ea | 104 159 | 4.1 What is Generative Artificial Intelligence (GenAI) | Generative Artificial Intelligence (generative AI, GenAI, or GAI) is a subset of artificial intelligence that can use Generative Adversarial Models (GANs) or Diffusion Model Architecture (DMAs) to produce text, images, videos, or other forms of data [i.1]. Instead of being based on the input, these models learn the und... |
13063999760325619f5f8127992828ea | 104 159 | 4.3.5.1 The Interim Measures for the Management of Generative AI Services | Under the AI Measures, "generative AI technology" [i.5] refers to models and related technology that have the ability to generate text, images, audio, videos, or other content. The key roles under the AI Measures are Generative AI service providers and users. "Generative AI service provider" refers to any organization ... |
13063999760325619f5f8127992828ea | 104 159 | 4.3.10 UK: AI Code of Practice | The scope of this voluntary Code of Practice [i.11] is focused on AI systems. This includes systems that incorporate deep neural networks, such as generative AI. The Code sets out cybersecurity requirements for the lifecycle of AI. These are secure design, secure development, secure deployment, secure maintenance and s... |
13063999760325619f5f8127992828ea | 104 159 | 4.3.11 USA | |
13063999760325619f5f8127992828ea | 104 159 | 4.3.11.1 California | |
13063999760325619f5f8127992828ea | 104 159 | 4.3.11.1.1 AB 2013 Generative artificial intelligence: training data transparency | AB 2013 [i.12] requires developers of GenAI systems to publicly disclose detailed information about the datasets used in their development on their website. The law's transparency mandate applies to all GenAI systems and services made available to Californians, regardless of whether compensation is involved, provided t... |
13063999760325619f5f8127992828ea | 104 159 | 5 Impact of GenAI on Intellectual Property Rights | |
13063999760325619f5f8127992828ea | 104 159 | 5.1 Overview | Generally, Generative AI systems are typically trained on large available datasets which may include copyrighted works, personal information, biometric data, and harmful and illegal content [i.18]. AI developers have argued that such training is protected under fair use, while copyright holders have argued that it infr... |
13063999760325619f5f8127992828ea | 104 159 | 5.2 Copyright theft and infringement | The issues and problems of copyright are that AI generative software cannot create "original" media from zero; rather it needs a pre-existing training data input to bootstrap the algorithms through a machine learning model [i.19]. The origin of those images/input is crucial not only regarding the ownership of the copyr... |
13063999760325619f5f8127992828ea | 104 159 | 6 Harmful Impacts from GenAI | 6.1 Overview Generative AI has a multitude of issues and risks pertaining to, but not limited to, the distribution of harmful content, copyright and legal exposure, sensitive information disclosure, amplification of existing bias, data provenance, lack of explicability/explainability and interpretability and hallucinat... |
13063999760325619f5f8127992828ea | 104 159 | 6.5 Loss of Confidentiality | The risk of loss of confidentiality from GenAI can occur because the Large Language Models (LLMs), the backbone of many GenAI systems, can inadvertently or maliciously leak sensitive information. This can occur through various means, such as data breaches, inadvertent disclosures, or sophisticated cyberattacks that exp... |
13063999760325619f5f8127992828ea | 104 159 | 6.7.2 Phishing | An AI phishing attack leverages artificial intelligence to make the phishing emails more convincing and personalized. A malicious actor could use AI algorithms to analyse vast amounts of data on a target segment, such as social media profiles, online behaviour, and publicly available information, which allows them to c... |
13063999760325619f5f8127992828ea | 104 159 | 8.1 Overview | A type of threat falling under the greater and more pervasive umbrella of synthetic media utilizes a form of artificial AI/ML to create believable, realistic videos, pictures, audio, and text of events which never happened [i.31]. Deepfakes are videos, audio, or images that seem real but have been manipulated with AI. ... |
13063999760325619f5f8127992828ea | 104 159 | 7 GenAI Content and Material | 7.1 How GenAI is shared and spreads online As with any user-created content, GenAI content and material are shared on all types of social media and related platforms. This difference is mainly the scale and amount of content that can be shared. For example, a digital artist uploads a finished piece once a week. A perso... |
13063999760325619f5f8127992828ea | 104 159 | 7.2 Best Practice Measures within GenAI Platforms / Services | 7.2.1 Prevention by Design Prevention involves efforts to limit the creation of harmful deepfakes. This can include adopting prompt filters to prevent models from being instructed to create certain types of content (e.g. nude content); removing harmful content from model training datasets; and blocking outputs before t... |
13063999760325619f5f8127992828ea | 104 159 | 8 Conclusion | 8.1 Overview There are patterns that link the threats from GenAI, the mitigations and the compliance to legislation and regulation. For developers of GenAI, by understanding the measures they have to comply with they can implement controls and polices. Often these controls and polices also mitigate harm from GenAI by m... |
13063999760325619f5f8127992828ea | 104 159 | 8.2 Trustworthy AI | 8.2.1 Overview Trustworthy AI is built upon three pillars that form the foundation of trustworthy AI as indicated in Figure 2, and necessitate adherence throughout the entire AI system lifecycle as presented in ETSI TS 104 119 [i.39]: • “Lawful: AI systems shall rigorously comply with all applicable legal and regulator... |
9616788112c1b81b85993ed947979ef9 | 104 166 | 1 Scope | The present document is a transposition of ITU-T Technical Report (02/2025) QSTR-GDM [i.1] without modifications. |
9616788112c1b81b85993ed947979ef9 | 104 166 | 2 References | |
9616788112c1b81b85993ed947979ef9 | 104 166 | 2.1 Normative references | Normative references are not applicable in the present document. |
9616788112c1b81b85993ed947979ef9 | 104 166 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
9616788112c1b81b85993ed947979ef9 | 104 166 | 3 Definition of terms, symbols and abbreviations | |
9616788112c1b81b85993ed947979ef9 | 104 166 | 3.1 Terms | For the purposes of the present document, the terms given in ITU-T Technical Report QSTR-GDM [i.1] apply. |
9616788112c1b81b85993ed947979ef9 | 104 166 | 3.2 Symbols | Void. |
9616788112c1b81b85993ed947979ef9 | 104 166 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ITU-T Technical Report QSTR-GDM [i.1] apply. |
9616788112c1b81b85993ed947979ef9 | 104 166 | 4 Endorsement notice | All elements of Technical Report QSTR-GDM [i.1] apply. ITU-T Technical Report QSTR-GDM [i.1] is contained in archive tr_104166v010101p0.zip which accompanies the present document. ETSI ETSI TR 104 166 V1.1.1 (2025-12) 6 History Version Date Status V1.1.1 December 2025 Publication |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 1 Scope | The present document provides the Test Suite Structure (TSS) and Test Purposes (TP) for the test specification for the IP/ICMP Translation Algorithm as specified in IETF RFC 7915 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.2] and ETSI ETS 300 ... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 2 References | |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 3 Definition of terms, symbols and abbreviations | |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 3.1 Terms | For the purposes of the present document, the terms given in IETF RFC 7915 [1] and the following apply: Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [i.1]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [i.1]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [i.1]. Test Purpose (TP): Refer to ISO/IEC... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 3.2 Symbols | Void. |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in IETF RFC 7915 [1] and the following apply: 3GPP 3rd Generation Partnership Project AH Authentication Header ATS Abstract Test Suite DF Don't Fragment ESP Encapsulating Security Payload GE Generation of ICMPv4/ICMPv6 Error message ICMP Internet Control... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 4 Test configurations | |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 4.1 Introduction | Test purposes of the present document address the IP/ICMP translators that is the implementation of stateless IP/ICMP translating algorithm. |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 4.2 Test configuration | Following configurations are simplified to highlight tested interface and involved entities. Figure 1: Test configuration CF_XLAT_SIIT |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5 Test Suite Structure (TSS) and Test Purposes (TP) | |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.1 Test Suite Structure | |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.1.1 TP naming convention | TPs are numbered, starting at 01, within each group. Groups are organized according to the TSS. Table 1: TP identifier naming convention scheme Identifier: <TP>_<scope>_<nn> <tp> = Test Purpose: fixed to "TP" <interface or protocol> Interface or protocol: stateless IP/ICMP translation (SIIT) algorithm <direction> from ... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.1.2 Test strategy | As the base specification in IETF RFC 7915 [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification ETSI TS 104 153-1 [2]. |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.1.3 TP structure | Each TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPs more readable and checkable. A particular structure has been used which is illustrated in Table 2. Table 2 should be read in conjunction with any TP, i.e. use a TP as an example to facilitate the full c... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2 Test Purposes | |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.1 PICS references | All PICS items referred to in this clause are as specified in ETSI TS 104 153-1 [2] unless indicated otherwise by another numbered reference. PICS items are only meant for test selection, therefore only PICS items with status optional or conditional are explicitly mentioned. |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.2 Translating from IPv4 to IPv6 | |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.2.1 Translating IPv4 Headers to IPv6 Headers | TP Id TP_SIIT_T46_IPHDR_01 Test Objective Verify that the IUT successfully adjust the threshold of the minimum IPv6 MTU to a value greater than 1 280 bytes. Reference IETF RFC 7915 [1], clause 4.1 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/1_1_1 Initial Conditions with { the IUT is configured with the IPv6 prefi... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.2.2 Translating ICMPv4 Headers to ICMPv6 Headers | TP Id TP_SIIT_T46_ICMPH_01 Test Objective Verify that the IUT successfully adjusts the type values of Echo messages (type 8) to 128, and adjusts the ICMP checksum both to take the type change into account and to include the ICMPv6 pseudo-header. Reference IETF RFC 7915 [1], clause 4.2 Configuration CF_XLAT_SIIT PICS Se... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.2.3 Translating ICMPv4 Error Messages into ICMPv6 | TP Id TP_SIIT_T46_ ICMPE_01 Test Objective Verify that the IUT successfully translates IPv4 packet inside the ICMPv4 . Reference IETF RFC 7915 [1], clause 4.3 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/1_3_1, 1_3_2 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.2.4 Generation of ICMPv4 Error Message | TP Id TP_SIIT_T46_GE_01 Test Objective Verify that the IUT sends back an ICMPv4 error message to the original sender of the packet if the IPv4 packet is discarded. Reference IETF RFC 7915 [1], clause 4.4 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/1_4_1, 1_4_2 Initial Conditions with { the IUT is configured with ... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.2.5 Transport-Layer Header Translation | TP Id TP_SIIT_T46_TLH_01 Test Objective Verify that IUT recalculates and updates TCP headers when the address translation algorithm is not checksum neutral. Reference IETF RFC 7915 [1], clause 4.5 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/1_5_1 Initial Conditions with { the IUT is configured with the IPv6 prefi... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.2.6 Knowing When to Translate | TP Id TP_SIIT_T46_KWT_01 Test Objective Verify that the IUT provides a normal forwarding function. Reference IETF RFC 7915 [1], clause 4.6 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/1_6_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 ... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.3 Translating from IPv6 to IPv4 | |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.3.1 Translating IPv6 Headers to IPv4 Headers | TP Id TP_SIIT_T64_IPHDR_01 Test Objective Verify that the IUT successfully translates IPv6 header into IPv4 header if there is no IPv6 Fragment Header. Reference IETF RFC 7915 [1], clause 5.1 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_1_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.3.2 Translating ICMPv6 Headers into ICMPv4 Headers | TP Id TP_SIIT_T64_ICMPH_01 Test Objective Verify that the IUT successfully translates Echo Request messages (128), adjusts the type value to 8 and recalculates the ICMP checksum both to take the type change into account and to exclude the ICMPv6 pseudo-header. Reference IETF RFC 7915 [1], clause 5.2 Configuration CF_XL... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.3.3 Translating ICMPv6 Error Messages into ICMPv4 | TP Id TP_SIIT_T64_ICMPE_01 Test Objective Verify the IUT translates the ICMP error messages containing the packet in error just like a normal IP packet (except that the TTL/Hop Limit value of the inner IPv4/IPv6 packet are not decremented), and update the Total Length field in the outer IPv4 header. Reference IETF RFC ... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.3.4 Generation of ICMPv6 Error Messages | TP Id TP_SIIT_T64_GE_01 Test Objective Verify that the IUT sends back an ICMPv6 error message to the original sender of the packet if the IPv6 packet is discarded. Reference IETF RFC 7915 [1], clause 5.4 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_4_1, 2_4_2 Initial Conditions with { the IUT is configured with ... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.3.5 Transport-Layer Header Translation | TP Id TP_SIIT_T64_TLH_01 Test Objective Verify that IUT recalculates and updates TCP headers when the address translation algorithm is not checksum neutral. Reference IETF RFC 7915 [1], clause 5.5 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_5_1 Initial Conditions with { the IUT is configured with the IPv6 prefi... |
81da142806d821d089f8c8d3fbf2d020 | 104 153-2 | 5.2.3.6 Knowing When to Translate | TP Id TP_SIIT_T64_KWT_01 Test Objective Verify that the IUT provides a normal forwarding function. Reference IETF RFC 7915 [1], clause 5.6 Configuration CF_XLAT_SIIT PICS Selection PICS_A2/2_6_1 Initial Conditions with { the IUT is configured with the IPv6 prefix and the IPv4 address pool the value of the minimum IPv6 ... |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 1 Scope | The present document provides a universal, inclusive structured framework-repository directory that identifies cybersecurity activity clusters and associated commonly used specifications that entail information exchange and associated information repositories. Responsible parties, network location and availability are ... |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 2 References | |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 3 Definition of terms, symbols and abbreviations | |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 3.1 Terms | For the purposes of the present document, the following terms apply: automation: use of technology, often including AI and machine learning, to automate cybersecurity processes, reducing human intervention and improving the efficiency of security operations bill of materials: document that lists the software or hardwar... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.