FIPS 198-1
E192652
FIPS 198-1 is a U.S. federal information processing standard that specifies the security requirements and implementation details for the HMAC (Hash-based Message Authentication Code) algorithm.
All labels observed (4)
| Label | Occurrences |
|---|---|
| FIPS 198 | 2 |
| FIPS 198-1 canonical | 1 |
| FIPS 198-1 Revision | 1 |
| FIPS PUB 198-1 | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1711776 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FIPS 198-1 Context triple: [HMAC, standardizedIn, FIPS 198-1]
-
A.
NIST SP 800-38D
NIST SP 800-38D is a NIST special publication that specifies the Galois/Counter Mode (GCM) of operation for the Advanced Encryption Standard (AES) and provides guidelines for its secure use.
-
B.
NIST SP 800-56C
NIST SP 800-56C is a NIST Special Publication that provides recommendations for key derivation methods in key-establishment schemes used in cryptographic systems.
-
C.
NIST SP 800-56B
NIST SP 800-56B is a NIST Special Publication that provides recommendations for cryptographic key establishment using RSA-based key transport and key agreement schemes.
-
D.
NIST SP 800-56A
NIST SP 800-56A is a NIST Special Publication that specifies approved methods for public-key establishment, including Diffie–Hellman–based key agreement schemes, for use in U.S. federal cryptographic systems.
-
E.
RFC 8017
RFC 8017 is the Internet standard that specifies the RSA Cryptography Standard (PKCS #1), defining algorithms and formats for RSA encryption and digital signatures.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: FIPS 198-1 Target entity description: FIPS 198-1 is a U.S. federal information processing standard that specifies the security requirements and implementation details for the HMAC (Hash-based Message Authentication Code) algorithm.
-
A.
NIST SP 800-38D
NIST SP 800-38D is a NIST special publication that specifies the Galois/Counter Mode (GCM) of operation for the Advanced Encryption Standard (AES) and provides guidelines for its secure use.
-
B.
NIST SP 800-56C
NIST SP 800-56C is a NIST Special Publication that provides recommendations for key derivation methods in key-establishment schemes used in cryptographic systems.
-
C.
NIST SP 800-56B
NIST SP 800-56B is a NIST Special Publication that provides recommendations for cryptographic key establishment using RSA-based key transport and key agreement schemes.
-
D.
NIST SP 800-56A
NIST SP 800-56A is a NIST Special Publication that specifies approved methods for public-key establishment, including Diffie–Hellman–based key agreement schemes, for use in U.S. federal cryptographic systems.
-
E.
RFC 8017
RFC 8017 is the Internet standard that specifies the RSA Cryptography Standard (PKCS #1), defining algorithms and formats for RSA encryption and digital signatures.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
U.S. federal information processing standard
ⓘ
cryptographic standard ⓘ |
| abbreviation |
FIPS 198-1
self-linksurface differs
ⓘ
surface form:
FIPS PUB 198-1
|
| appliesTo |
U.S. government agencies
ⓘ
federal information systems ⓘ |
| conformsTo | NIST cryptographic standards framework ⓘ |
| countryOfOrigin |
United States of America
ⓘ
surface form:
United States
|
| defines |
HMAC
ⓘ
Hash-based Message Authentication Code ⓘ
surface form:
Keyed-Hash Message Authentication Code
|
| definesConcept |
HMAC key
ⓘ
HMAC output ⓘ inner hash computation ⓘ outer hash computation ⓘ |
| domain |
cryptography
ⓘ
information security ⓘ |
| fullName |
HMAC
ⓘ
surface form:
The Keyed-Hash Message Authentication Code (HMAC)
|
| governs | use of HMAC in U.S. federal systems ⓘ |
| hasComponent |
implementation guidance for HMAC
ⓘ
normative specification of HMAC ⓘ security considerations for HMAC ⓘ |
| includes | test vectors for HMAC ⓘ |
| language | English ⓘ |
| publishedBy |
National Institute of Standards and Technology
ⓘ
U.S. Department of Commerce ⓘ |
| purpose |
to ensure data integrity and authenticity
ⓘ
to provide a mechanism for message authentication using cryptographic hash functions ⓘ |
| relatedTo |
SHA-2
ⓘ
surface form:
FIPS 180-4
HMAC-based authentication mechanisms ⓘ Secure Hash Standard ⓘ |
| replaces |
FIPS 198-1
self-linksurface differs
ⓘ
surface form:
FIPS 198
|
| specifies |
HMAC generation
ⓘ
HMAC verification ⓘ implementation details for HMAC ⓘ security requirements for HMAC ⓘ |
| status | superseded ⓘ |
| subject |
cryptographic authentication
ⓘ
data integrity ⓘ message authentication ⓘ |
| supersededBy |
FIPS 198-1
self-linksurface differs
ⓘ
surface form:
FIPS 198-1 Revision
|
| supersedes |
FIPS 198-1
self-linksurface differs
ⓘ
surface form:
FIPS 198
|
| targetAudience |
cryptographic module implementers
ⓘ
federal IT security personnel ⓘ system designers ⓘ |
| typeOfRequirement | mandatory for U.S. federal agencies when applicable ⓘ |
| usedIn |
federal cryptographic modules
ⓘ
security protocols requiring message authentication ⓘ |
| uses | cryptographic hash functions ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: FIPS 198-1 Description of subject: FIPS 198-1 is a U.S. federal information processing standard that specifies the security requirements and implementation details for the HMAC (Hash-based Message Authentication Code) algorithm.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
FIPS PUB 198-1
this entity surface form:
FIPS 198
this entity surface form:
FIPS 198
this entity surface form:
FIPS 198-1 Revision