ZeroHour
DashboardNewsCVEsExploitsIncidentsAIBriefAnalyticsEntitiesWatchlistIOCsAsk the feedSourcesFeeds & APIKiosk mode

Search: “Huntress customer”

2 stories in the last 3d

Searchkeywordsmart Sortlatesthotimportancerelevance
DomainAllCyberAIWindow24h3d7d30dAllIn the wildImportant onlyShow duplicates
CategoryAllData breach 1Industry 1
SeverityAllcritical 0high 1medium 0low 0info 1

Operational Resilience: IT Security Risks with Reduced Staffing | Huntress

Huntress blog advises security teams on managing change, risk, and incident response during reduced-staffing holiday periods.

The article discusses how holiday-period staffing reductions change organizational risk profiles around change management, monitoring, and incident response capability. It argues against blanket change freezes when critical vulnerabilities with high exploitation probability demand patching, and stresses retaining decision-making authority, escalation paths, and recovery knowledge. It concludes by promoting Huntress Managed Response, which lets the Huntress SOC take predefined containment actions on confirmed threats without customer intervention.

Huntress · 1d agoIndustry

Revolut Confirms Data Breach Through Fake Government Requests

Revolut disclosed customers' IDs, selfies, and financial data to impostors sending fraudulent requests from a legitimate government email domain.

Revolut confirmed an unauthorized third party obtained sensitive customer records by submitting fraudulent information requests from a legitimate government agency email domain with valid domain authentication, which employees fulfilled as standard legal compliance. Exposed data reportedly includes names, dates of birth, addresses, phone numbers, email addresses, occupations, passport and driver's license copies, verification selfies, IBANs, account-opening dates, transaction and withdrawal histories, and Bitcoin wallet references. Revolut says only a 'very limited group of customers' was affected, that systems and funds were untouched, and that it blocked the address and notified the agency, law enforcement, and regulators. Researcher ZachXBT first publicized the breach via Telegram on September 12.

Infosecurity Magazine · 2d agoData breach 3 sources