Martini Security retweeted
The FCC proposed a $2 million penalty on a voice service provider for allegedly applying improper attestation levels on calls it originated and authenticated with STIR/SHAKEN. This notice has some lessons for other providers. Read More: transnexus.com/blog/2024/pro…
Martini Security retweeted
Replying to @SecurityMartini
@SecurityMartini is, in my opinion, the best STIR/SHAKEN CA in the program. I'm proud to be both a client and an occasional contributor.
The STIR/SHAKEN ecosystem is soon transitioning to a new Certificate Policy. @SecurityMartini is still awaiting approval to begin issuing under it. With that said we remain hopeful about receiving this approval soon.
In preparation we have updated the STIR/SHAKEN Ecosystem Compliant Report (ecosystemcompliance.martinis…) and its associated tests to support these new requirements.
At this time we do not see any certificates issued under this policy. Given past adoption timelines it is hard to predict when that might happen. For example, the first CP was published in 2020, and CAs are supposed to comply with a new CP within 90 days of that. Despite this, many issuers today are still issuing certificates under the this old CP they were originally approved under.
This is noteworthy because there have been 3 other versions since then. To put a finer point on it, it has been 168 days since CP 1.4 was approved and there are no compliant certificates in use from what we can tell.
On a more positive note, it does appear that the STI-PA and PMA have been making some efforts to improve the processes as feedback is flowing more promptly now and there are subtle signs they may be taking compliance issues more seriously moving forward.
With all that said we are proud of our track record of being open, giving back to this ecosystem and being the most compliant CA within this ecosystem.
Martini Security retweeted
The STIR/SHAKEN ecosystem is soon transitioning to a new Certificate Policy. @SecurityMartini is still awaiting approval to begin issuing under it. With that said we remain hopeful about receiving this approval soon.
In preparation we have updated the STIR/SHAKEN Ecosystem Compliant Report (ecosystemcompliance.martinis…) and its associated tests to support these new requirements.
At this time we do not see any certificates issued under this policy. Given past adoption timelines it is hard to predict when that might happen. For example, the first CP was published in 2020, and CAs are supposed to comply with a new CP within 90 days of that. Despite this, many issuers today are still issuing certificates under the this old CP they were originally approved under.
This is noteworthy because there have been 3 other versions since then. To put a finer point on it, it has been 168 days since CP 1.4 was approved and there are no compliant certificates in use from what we can tell.
On a more positive note, it does appear that the STI-PA and PMA have been making some efforts to improve the processes as feedback is flowing more promptly now and there are subtle signs they may be taking compliance issues more seriously moving forward.
With all that said we are proud of our track record of being open, giving back to this ecosystem and being the most compliant CA within this ecosystem.
Martini Security retweeted
How do you leak an OEM private key for a trusted boot system. What kind of incompetence leads to that key ever being in a place where it can leak. And if that key can leak, what secret keys aren’t going to leak?
Martini Security retweeted
Today @FCC Chairwoman @JRosenworcelFCC and Illinois Attorney General @KwameRaoul announced a formal partnership to protect consumers against robocall scams. To date, 44 states have agreed to partnership with the @FCC’s Enforcement Bureau. fcc.gov/document/fcc-illinoi…
Martini Security retweeted
The @FCC’s Robocall Response Team today announced cease-and-desist letters warning 2 voice service providers to end their apparent support of illegal #robocalls or face serious consequences. fcc.gov/document/fcc-warns-m…
Martini Security retweeted
👉#FCC pending new rule eliminates 7-day waiting period for carriers to notify customers of breach.
All breaches must be reported to FCC, FBI & Secret Serv as soon as intrusions are discovered & immediately to consumers.
Definition of breach also updated
cyberscoop.com/fcc-data-brea…
Martini Security retweeted
What I’m seeing constantly is calls which presumably started with a signature and lost it in transit. There’s a lot of TDM remaining in the middle. Additionally, I theorize that there are more IP NNIs than have been acknowledged where Identity is getting stripped.
Martini Security retweeted
Gateway providers have until 1/11/23 to submit Robocall Mitigation Database certifications including #robocall mitigation plans. If they aren’t in the database by 4/11/23, then other voice service providers will be prohibited from accepting their traffic. fcc.gov/document/wcb-announc…
Martini Security retweeted
Today the @FCC proposed rules for notifying customers and federal law enforcement of breaches of customer proprietary network information to better align its rules with federal & state data breach laws covering other sectors. fcc.gov/document/fcc-propose…
Martini Security retweeted
The robocall mitigation call source signing system (SHAKEN/STIR) that the @FCC now requires has some interesting stats. Most calls are still not signed. And many robocalls ARE signed, but there seems to be no enforcement, yet. transnexus.com/blog/2023/sha…
Martini Security retweeted
The FCC announced its decision on whether the STIR/SHAKEN implementation extension for small providers should be extended further or lapse. Details: transnexus.com/blog/2022/fcc…
Martini Security retweeted
Still confused about robocall mitigation efforts over the past year? John Haraburda breaks it down in this end of year @RCRWireless piece: https://teapawt.org/t.co/tNaiWbzOtV
Martini Security retweeted
Telecom is a far-reaching, unbelievably intricate landscape. The only way we can properly control it and the risks it faces is by working together, as Timo Vainionpaa illustrates in this quote.
#TimoVainionpaa
Martini Security retweeted
The monthly STIR/SHAKEN statistics improved slightly in November. Is this a blip, or a new trend? Details: transnexus.com/blog/2022/sha…
Martini Security retweeted
For the first time, a voice service provider is being cut off from other networks for failing to meet the FCC’s requirements for protecting consumers against scam #robocalls and malicious caller ID #spoofing. fcc.gov/document/fcc-cuts-pr…
Martini Security retweeted
Over 400 Downloads of the RAG Fraud Catalog commsrisk.com/over-400-downl…
Martini Security retweeted
🚨 NEW: CVE-2022-26499 🚨 An SSRF issue was discovered in Asterisk through 19.x. When using STIR/SHAKEN, it's possible to send arbitrary requests (such as GET) to interfaces such as localhost by using the Identity he... (click for more) Severity: CRITICAL nvd.nist.gov/vuln/detail/CVE…
Martini Security retweeted
New Article: As More Countries Consider International Call Authentication Standards, What Can Regulators Learn from STIR/SHAKEN? dlvr.it/Scz8PR
Martini Security retweeted
Can’t believe the number of spam/robocalls coming thru @metronetfiber every day. Upwards of 20-30 calls per day. After speaking to them it appears they do not participate in #StirShaken framework.
@FCC requires implementation by June 30,2023.


















