Using signed tokens to verify short message service (SMS) message bodies
Aspects of the disclosure relate to message verification. A computing platform may generate a cryptographic key pair comprising a public key and a private key. The computing platform may publish, to a server, the public key. The computing platform may generate a short message service (SMS) message. The computing platform may sign, using the private key, the SMS message, which may include computing a cryptographic hash of the SMS message using the private key and embedding the cryptographic hash in an SMPP field of the SMS message. The computing platform may send, to a downstream computing system, the signed SMS message, where the downstream computing system may be configured to validate the signed SMS message using the cryptographic hash embedded in the SMPP field of the SMS message and by accessing the public key.
1. A computing platform, comprising:
at least one processor;
a communication interface communicatively coupled to the at least one processor; and
memory storing computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:
generate a cryptographic key pair comprising a public key and a private key;
publish, to a server, the public key; generate a short message service (SMS) message;
sign, using the private key, the SMS message, wherein signing the SMS message comprises computing a cryptographic hash of the SMS message using the private key and embedding the cryptographic hash in a short message peer-to-peer (SMPP) field of the SMS message; and
send, to a downstream computing system, the signed SMS message, wherein the downstream computing system is configured to validate the signed SMS message using the cryptographic hash embedded in the SMPP field of the SMS message and by accessing the public key from an internet Domain Name Service (DNS) server of a domain indicated by the computing platform.
2. The computing platform of claim 1 , wherein signing the SMS message causes message metadata to indicate retrieval information for the public key.
3. The computing platform of claim 1 , wherein the server comprises a DNS server.
4. The computing platform of claim 1 , wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, cause the computing platform to perform one or more of:
store, at the computing platform, the private key, or
upload, to a Communications Platform as a Service (CPaaS) platform, the private key, wherein the private key is stored at the CPaaS platform.
5. The computing platform of claim 4 , wherein signing the SMS message comprises signing the SMS message at one of: the computing platform or the CPaaS platform.
6. The computing platform of claim 1 , wherein computing the cryptographic hash of the SMS message comprises hashing one or more of: contents of the SMS message and sender information.
7. The computing platform of claim 1 , wherein the SMPP field comprises a custom SMPP tagged link value (TLV).
8. The computing platform of claim 1 , where the SMS message is additionally signed by an upstream intercarrier computing system using another public-private key combination, and wherein the downstream computing system further verifies the complete SMS message based on the upstream intercarrier computing system's signature.
9. The computing platform of claim 1 , wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:
receive, from the downstream computing system, a message indicating that a problem occurred with signature validation for the SMS message.
10. The computing platform of claim 9 , wherein the message indicating that a problem occurred with signature validation for the SMS message may indicate that the problem comprises one or more of: a message payload modification, a message payload corruption, or an issue with truncation of payload for the SMS message during transit.
11. The computing platform of claim 9 , wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:
generate, based on receipt of the message indicating that the problem occurred with signature validation for the SMS message, an abuse reporting format (ARF) message, wherein the ARF message includes one or more policies indicating how downstream computing systems, including the downstream computing system, should handle messages that are unable to be validated.
12. The computing platform of claim 11 , wherein generating the ARF message causes the computing platform to instruct the downstream computing systems to: deliver the invalid messages with a warning, quarantine the invalid messages, send the invalid message in a digest, or drop the invalid message.
13. A method comprising:
at a computing platform comprising at least one processor, a communication interface, and memory:
generating a cryptographic key pair comprising a public key and a private key;
publishing, to a server, the public key;
generating a short message service (SMS) message;
signing, using the private key, the SMS message, wherein signing the SMS message comprises computing a cryptographic hash of the SMS message using the private key and embedding the cryptographic hash in an SMPP field of the SMS message; and
sending, to a downstream computing system, the signed SMS message, wherein the downstream computing system is configured to validate the signed SMS message using the cryptographic hash embedded in the SMPP field of the SMS message and by accessing the public key from an internet Domain Name Service (DNS) server of a domain indicated by the computing platform.
14. The method of claim 13 , wherein signing the SMS message causes message metadata to indicate retrieval information for the public key.
15. The method of claim 13 , wherein the server comprises a DNS server.
16. The method of claim 13 , further comprising performing one or more of:
storing, at the computing platform, the private key, or
uploading, to a Communications Platform as a Service (CPaaS) platform, the private key, wherein the private key is stored at the CPaaS platform.
17. The method of claim 16 , wherein signing the SMS message comprises signing the SMS message at one of: the computing platform or the CPaaS platform.
18. The method of claim 13 , wherein computing the cryptographic hash of the SMS message comprises hashing one or more of: contents of the SMS message and sender information.
19. The method of claim 13 , wherein the SMPP field comprises a custom SMPP tagged link value (TLV).
20. One or more non-transitory computer-readable media storing instructions that, when executed by a computing platform comprising at least one processor, a communication interface, and memory, cause the computing platform to:
generate a cryptographic key pair comprising a public key and a private key;
publish, to a server, the public key;
generate a short message service (SMS) message;
sign, using the private key, the SMS message, wherein signing the SMS message comprises computing a cryptographic hash of the SMS message using the private key and embedding the cryptographic hash in an SMPP field of the SMS message; and
send, to a downstream computing system, the signed SMS message, wherein the downstream computing system is configured to validate the signed SMS message using the cryptographic hash embedded in the SMPP field of the SMS message and by accessing the public key from an internet Domain Name Service (DNS) server of a domain indicated by the computing platform.