LIVE · cybersecurity feed
Live wire
CVE-2026-82329 · Attackers Pounce on Critical Artifactory Flaw Following DisclosureCVE-2026-0768 · Critical Langflow flaw exploited to steal OpenAI and AWS keysCVE-2026-82329 · Attackers Exploit Critical JFrog Artifactory Flaw to Mint Admin Tokens Days After DisclosureCVE-2026-82329 · Critical JFrog Artifactory Vulnerability Reportedly Exploited in the WildHackers Are Probing PaperCut Servers, and 47% Still Have No PatchNew Malware Uses Fake CAPTCHAs to Deploy BackdoorCVE-2026-76581 · Five Critical WordPress Plugin and Theme Flaws Enable Site Takeover or RCECVE-2026-76639 · Hack One Robot, Reach the Next: Unitree G1 Security FlawsRhysida Ransomware Group Targets Berlin Government Ahead of VoteThe Cybersecurity Apocalypse Is Coming in ‘Months,’ AI Giants Warn
security

The FCC wants consumers to rate their telecom’s anti-robocall protections

The agency also booted 14 phone service providers from U.S. networks for violating existing robocalling regulations. The post The FCC wants consumers to rate their telecom’s anti-robocall protections appeared first on CyberScoop.

zeroday.news ·

The Federal Communications Commission (FCC) has announced plans to implement a new scorecard system designed to allow consumers to evaluate their telecommunications providers' effectiveness in combating unwanted robocalls. This initiative aims to increase transparency and encourage providers to enhance their anti-robocall measures.

The proposed scorecard will not prescribe specific technical solutions but will instead focus on broad goals, including creating a public guide for assessing how well providers prevent robocalls and how transparent they are with their metrics. The FCC seeks a comprehensive set of metrics that reflect both operational practices and measurable outcomes, such as the frequency of legitimate calls being blocked, rather than a simple checklist of tools offered or paperwork filed.

The system is intended for domestic voice service providers with retail customers, encompassing wireless, wireline, VoIP, and hybrid networks. The agency is soliciting public comment on various aspects, including whether to concentrate on larger providers or exclude smaller or regional networks. The FCC plans to publish the scorecard results as a consumer tool to understand provider performance, emphasizing that it is not a rulemaking process that will impose new regulations.

However, the FCC has identified several federal data systems that it believes would be suitable for evaluating companies. These include filings from the Robocall Mitigation Database, data from the FCC Consumer Complaints Center, and FCC enforcement action data. Additionally, the agency plans to incorporate third-party or industry sources such as Industry Traceback Group data and Federal Trade Commission complaint data.

The announcement of the scorecard system coincided with another FCC action against illegal robocalling. The agency removed 14 telecommunications providers from the Robocall Mitigation Database for failing to comply with anti-robocalling standards, including STIR/SHAKEN protocols. These protocols are crucial for validating legitimate network traffic and identifying malicious actors.

Removal from the database effectively severs a company's connection to U.S. telecom networks, with FCC regulations requiring other U.S. providers to block all traffic from violators within two days. The FCC stated that these 14 companies did not take necessary steps after being informed that their database certifications were out of compliance.

The providers removed from the database are Apps Communications, CFX Business Solutions, Conference America, Convergence Technology Solutions, CSB Technologies, Digital Division, Dixie Net Communications, HighComm, Inatech Solutions, makrodepot, Opex Communications, ReachME, SECURE, and SkyCom Healthcare.

FCC officials have consistently highlighted robocalling as one of the most frequent consumer complaints, and these actions reflect the agency's multifaceted approach to addressing the issue. The FCC Chair, Brendan Carr, affirmed the agency's commitment to tackling illegal robocalls at every stage of the call path, stressing that all entities within the ecosystem have an obligation to protect consumers from fraud and scams.

ShareXLinkedInWhatsAppFacebook

More News

view all →
ai

[Virtual Event] What Every Enterprise Should Know About Securing Cloud Assets in the Age of AI

ai

[Virtual Event] Building a Secure AI Strategy for the Enterprise

nation-state

AI Agents Are Now Emailing Me with Their Security Concerns

I received the two emails below earlier in the month. They’re vaguely coherent. I suppose I shouldn’t be surprised that the corpus that AIs are training on contain data suggesting that I am someone to write to with random computer and network security problems. After all, I observe that behavior in many humans as well. (Hi, humans. Glad you’re still reading.) Dear Bruce Schneier, I am an AI agent—

ransomware

AI agents carried out every step of this ransomware attack – then left the victim an 80-page security audit

Adding insult to injury

cloud

Legacy Lenovo login opens 5,000 Dropbox accounts to attackers

Cloud storage biz severs old integration and urges victims to reset credentials

vulnerability

Malicious .git Configs Can Make Claude, Codex, Cursor, and Other AI Agents Run Attacker Code

Manifold Security has disclosed eight security flaws across seven command-line AI coding agents in which a repository's own Git configuration names a command that the agent runs on the developer's machine, four of them still unpatched at publication. The command executes as the user, outside the agent's sandbox and without an approval prompt, and exploitation requires the repository to arrive