Gertrude

Gertrude

@baly56.bsky.social

“It's a universal law - intolerance is the first sign of an inadequate education. An ill-educated person behaves with arrogant impatience, whereas truly profound education breeds humility.” Aleksandr Solzhenitsyn

2.8K followers3.1K following5.7K posts

One of my worries.

Ian Weissman, DO@drianweissman.bsky.social

The first personalized mRNA cancer vaccine has now succeeded in a phase 3 clinical trial, reducing the risk of melanoma returning by 42% compared with standard immunotherapy alone. www.sciencealert.com/world-first-...

Gertrude reposted

This is a rare moment of bipartisanship. And a reliable indication that Darline Graham is a horrible, inexperienced nepo-candidate.

Jamie Dupree@jamiedupree.bsky.social

Two former Governors of South Carolina - one from each party - have endorsed Democrat Annie Andrews who is running against Sen. Darline Graham R-SC

Gertrude reposted

Gertrude reposted

The importance of salmon might be a novel idea to the Lower 48, but every Alaskan understands. Fish is how we feed our families, drive our economy, and sustain our way of life. I’m the only candidate fighting for our fisheries, not the factory trawlers.

newyorker.comAlaska’s Senate Race Could Be Decided by SalmonMary Peltola, the Democratic candidate for Alaska’s Senate seat, is a key part of the Party’s plan to retake Congress. She really just wants to talk about fish.

Gertrude reposted

Democrats have just released a 50-page report detailing Trump's mentions in the Epstein files. Democratic House Judiciary members have also called for an independent special counsel to investigate Trump and AG Todd Blanche's conflicts of interest in handling the files.

Gertrude reposted

"There's not much power without having a voice." Americans in a Freedom Forum video reminded us that the First Amendment lets us express ourselves, stand up for what's right, and protest when government strays. Democracy works when we speak up. Protect your rights and vote!

Grew up watching this show that was a cornucopia of social and science innovation. It taught me science was for anyone and that our ridiculous racism was wasted energy. Rest in peace and thanks to those who brought us the awakening of society —you are with us always Chekov.

Gertrude reposted

Top 10 Best Data Access Governance Tools in 2026 [Ranked & Scored]

cybersecuritynews.comTop 10 Best Data Access Governance Tools in 2026 [Ranked & Scored]Ask any enterprise “who can read the M&A folder?” and watch the room go quiet effective access is buried under nested groups, inherited shares, service-account grants, and warehouse roles nobody has reviewed since the migration. Data access governance (DAG) answers that question continuously and then shrinks the answer. It’s also 2026’s quiet AI prerequisite: every copilot deployment inherits your permission sprawl and surfaces it in chat. We scored ten tools on visibility truth, remediation muscle, and estate fit. Varonis takes 1 ; Veza and Immuta complete the podium. Key Takeaways • 1 overall: Varonis the effective-access graph plus automated least-privilege remediation at collaboration scale. • Podium: Varonis (remediation muscle), Veza (identity-to-data authorization graph), Immuta (warehouse-native policy). • Copilot effect: AI assistants surface every overexposed file to every user who technically has access DAG is the fix, not the chatbot settings. • Nonhuman identities: service accounts and pipelines now outnumber humans on data grants; govern them first. How We Scored (Methodology) Research-based evaluation: effective-access computation (nested groups, inheritance, cross-system), activity-informed right-sizing, automated remediation safety, access-review/certification workflows , estate coverage (collaboration, warehouse, SaaS, infrastructure), and pricing structure. No lab testing; no paid placement; editorial scores excluded from structured data. Weights: effective-access truth 30% , remediation automation 25%, estate coverage 20%, review workflows 15%, pricing clarity 10%. The 2026 Data Access Governance Power Rankings S.NO Tool Award Score* 1 Varonis Best effective-access remediation 9.1 2 Veza Best authorization graph 8.8 3 Immuta Best warehouse-native policy 8.6 4 Microsoft Purview Best M365-estate governance 8.4 5 SailPoint Best IGA-integrated data governance 8.3 6 BigID Best discovery-anchored governance 8.2 7 Netwrix Best mid-market auditing value 8.0 8 Privacera Best open-standard lakehouse control 7.9 9 Satori Best deploy-light warehouse access 7.8 10 Concentric AI Best semantic risk-based governance 7.7 *Editorial research-based scores, not lab results. 1. Varonis — Best Effective-Access Remediation Varonis — Best Effective-Access Remediation Snapshot: Per-user/quote | Permission graph + audit stream + automated fixes | SaaS-delivered Why it earns 1: Varonis computes what others estimate true effective access across nested groups and inheritance then watches actual usage and acts : automated removal of unused grants, global-access-group elimination, and continuous least-privilege enforcement that has shrunk blast radius at thousands of organizations. With Copilot-readiness assessments riding the same engine, it’s the category’s remediation benchmark, not just its dashboard. Pros: Remediation automation that actually executes; activity-informed decisions; deep M365/file-share/SaaS coverage. Cons: Warehouse/lakehouse depth lighter than policy-native rivals. Bottom line: Finds the sprawl, then deletes it safely. 2. Veza — Best Authorization Graph Veza — Best Authorization Graph Snapshot: Quote | Identity-to-data effective permissions across systems | NHI-strong Why it earns 2: Veza’s graph answers the cross-system question nobody else frames as crisply: this identity (human or service account) can take these actions on this data, across warehouses, SaaS, infrastructure, and apps Identity-to-data effective permissions across systems local roles translated into one effective-permission model. For the nonhuman-identity sprawl defining 2026, it’s the clearest lens on who-can-do-what. Pros: Cross-system authorization truth; NHI governance strength; access reviews on real permissions, not role names. Cons: Younger remediation muscle than Varonis in collaboration estates. Bottom line: The permissions graph your IGA tool thinks it has. 3. Immuta — Best Warehouse-Native Policy Immuta — Best Warehouse-Native Policy Snapshot: Quote/tiered | Plain-language ABAC policies | Native Snowflake/Databricks enforcement Why it earns 3: Immuta turns governance into enforced policy where analytics lives: attribute-based rules written once (“masks PHI except for care-team roles”) compile into native warehouse controls no proxies, no copies with discovery wiring detected sensitive columns straight into enforcement. The lakehouse lane’s policy anchor. Pros: Policy-as-code clarity; native pushdown enforcement; discovery-to-policy loop. Cons: Scoped to analytics platforms, not file/collab estates. Bottom line: Access governance the warehouse itself enforces. 4. Microsoft Purview — Best M365-Estate Governance Microsoft Purview — Best M365-Estate Governance Snapshot: E5/bundled | Labels, DLP, access reviews, Restricted SharePoint Search era | Copilot-driven urgency Why it earns 4: Copilot made Microsoft’s own governance stack urgent: Purview labels and DLP, Entra access reviews, SharePoint Advanced Management , and oversharing assessments form the native toolkit for taming M365 permission sprawl before AI amplifies it. It’s assembly-required several consoles, E5-tier licensing but it’s the estate’s first-party answer. Pros: Native depth; bundle economics at E5; Copilot-readiness alignment. Cons: Fragmented toolchain; effective-access truth still favors specialists. Bottom line: The first-party toolkit Copilot forced onto every roadmap. 5. SailPoint — Best IGA-Integrated Data Governance SailPoint — Best IGA-Integrated Data Governance Snapshot: Quote | Data Access Security (file-access governance) inside the IGA leader Why it earns 5: SailPoint extends identity governance to unstructured data Data Access Security (file-access governance) inside the IGA leader delivers discovery of overexposure, access reviews, and remediation requests in the same platform that already runs joiner-mover-leaver and certifications. For enterprises standardized on SailPoint IGA, folding data access into existing governance rhythms beats bolting on a parallel program. Pros: One governance program for apps and data; certification-campaign maturity. Cons: Analytics depth trails the data-native specialists. Bottom line: Data access inside the identity-governance machine. 6. BigID — Best Discovery-Anchored Governance BigID — Best Discovery-Anchored Governance Snapshot: Quote | Access intelligence on the discovery graph | Who-can-access-what-sensitive-data Why it earns 6: BigID starts from the data truth it already owns classified, correlated inventory and layers access intelligence: which identities can reach which sensitive classes, where open access meets regulated data, and remediation workflows scoped by sensitivity rather than folder names. Governance that knows what the data is first. Pros: Sensitivity-weighted access risk; one engine for discovery + governance; privacy-use synergy. Cons: Remediation execution depth behind Varonis. Bottom line: Access risk ranked by what the data actually is. 7. Netwrix — Best Mid-Market Auditing Value Netwrix — Best Mid-Market Auditing Value Snapshot: Licensed | Auditor + Data Classification + PolicyPak lineage | AD/file-share strength Why it earns 7: Netwrix gives mid-market teams the working core who has access, who used it, what changed, with classification context and review workflows across AD, file shares, and M365 at licensing that doesn’t require a platform committee. Pros: Approachable pricing/operations; strong AD/change context; suite synergy. Cons: Enterprise-scale graph analytics and automation lighter. Bottom line: The pragmatic mid-market governance workhorse. 8. Privacera — Best Open-Standard Lakehouse Control Privacera — Best Open-Standard Lakehouse Control Snapshot: Quote | Apache Ranger lineage | Unified policies across cloud data services Why it earns 8: Built by Ranger’s creators, Privacera applies unified policies across lakehouse and cloud data services attractive for platform teams wanting Ranger-compatible governance without proprietary lock-in, with encryption and masking in the same policy plane. Pros: Open-source lineage; multi-service policy unification. Cons: Ecosystem gravity behind Immuta in the lane. Bottom line: The open-standard path to lakehouse policy. 9. Satori — Best Deploy-Light Warehouse Access Satori — Best Deploy-Light Warehouse Access Snapshot: Tiered/quote | Proxy-based, agentless | JIT access + dynamic masking in hours Why it earns 9: Satori’s transparent access layer delivers governance outcomes just-in-time grants, dynamic masking, universal audit over Snowflake-class platforms in hours, no warehouse-side changes. The speed-to-governed pick when the mandate landed last quarter. Pros: Fastest deployment in the lane; self-service access flows. Cons: Proxy architecture is a design decision to accept. Bottom line: Warehouse governance measured in hours, not quarters. 10. Concentric AI — Best Semantic Risk-Based Governance Concentric AI — Best Semantic Risk-Based Governance Snapshot: Quote | Meaning-based sensitivity + peer-exposure analysis | Autonomous risk flags Why it earns 10: Concentric governs by semantics: it understands a document is a term sheet, compares its sharing against peer documents, and flags deviation surfacing the overshared contract no pattern rule would catch . A sharp unstructured-data lens that pairs well with heavier remediation engines. Pros: Catches context-dependent overexposure; low-rule-maintenance operation. Cons: Remediation and structured-data reach are the slimmer chapters. Bottom line: The risk flags your rules were never going to write. Full Comparison Table Tool Effective-access truth Auto-remediation Estate focus NHI coverage Pricing Varonis Deep (collab/file) Best-in-class M365/shares/SaaS Partial Per-user Veza Cross-system graph Workflow-driven Warehouse/SaaS/infra Strong Quote Immuta Policy-computed Policy-native Lakehouse Partial Quote Purview M365-scoped Partial M365/Azure Partial Bundled (E5) SailPoint Via IGA + DAS Request-driven Apps + files Growing Quote BigID Sensitivity-weighted Workflow Broad data planes Partial Quote Netwrix AD/share-scoped Partial Mid-market estates Partial Licensed Privacera Policy-computed Policy-native Lakehouse Partial Quote Satori Proxy-observed JIT-native Warehouse Partial Tiered Concentric Semantic peer-based Flag + workflow Unstructured No Quote Yes/No Capability Table Tool Effective-access graph? Automated grant removal? Access certifications? Warehouse-native enforcement? Copilot/AI-readiness module? Varonis Yes Yes Yes Partial Yes Veza Yes (cross-system) Partial Yes Partial Yes Immuta Yes (policy scope) Yes (policy) Partial Yes Partial Purview Partial Partial Yes (Entra) No Yes SailPoint Partial Partial Yes No Partial BigID Yes Partial Yes No Yes Netwrix Partial Partial Yes No Partial Privacera Yes (policy scope) Yes (policy) Partial Yes No Satori Yes (proxy scope) Yes (JIT expiry) Partial Via proxy Partial Concentric Partial (semantic) No Partial No Yes Buying Advice: Fix One Folder, Then Trust the Automation Prove value on the crown jewels first: pick your most sensitive repository, have each finalist compute true effective access (nested groups and service accounts included compare against a manual audit), then let it right-size based on actual usage and measure how many grants die without a single access complaint. That one exercise exposes the category’s real differences: graph truth, remediation safety, and rollback discipline. Scope by estate collaboration sprawl → Varonis; cross-system authorization and NHIs → Veza; lakehouse → Immuta/Privacera/Satori by deployment taste; IGA-standardized shops → SailPoint’s extension. If Copilot or an equivalent assistant is deploying, run an oversharing assessment before enablement AI turns latent overexposure into daily exposure. And put nonhuman identities in the first certification campaign, not the someday list; they hold the widest grants and answer to nobody’s manager. FAQs What is the best data access governance tool in 2026? Varonis ranks 1 for effective-access truth plus automated remediation, Veza for the cross-system authorization graph, and Immuta for warehouse-native policy with Purview the M365 first-party toolkit and Netwrix the mid-market value pick. How is DAG different from IGA? IGA governs accounts and app entitlements; DAG governs what identities can actually do to data resolving nested groups, shares, and warehouse roles into effective access, then shrinking it . Mature programs connect both (SailPoint and Veza sit at that junction). Why did Copilot make DAG urgent? AI assistants retrieve anything the asking user can technically access permission sprawl that hid behind obscurity becomes one prompt away. Oversharing assessment and least-privilege remediation are the prerequisite, not a post-launch fix. What about service accounts and pipelines? Nonhuman identities now dominate data grants and are never recertified by habit. Demand NHI visibility (Veza-class) and include them in review campaigns from day one. How do we run access reviews that aren’t rubber stamps? Review effective access with usage evidence attached “can read, hasn’t in 14 months” and default to removal with easy re-grant. Tools that present role names without usage data produce the rubber stamps you’re trying to escape. Verdict Varonis deletes the sprawl, Veza maps it across every system that grants it, Immuta compiles policy into the warehouse itself, and Purview is the first-party kit Copilot made mandatory pilot on your crown-jewel folder, certify the service accounts first, and judge every tool by grants removed without complaints, the category’s only honest metric. Author: [AUTHOR NAME], [credential]. Reviewed by: [REVIEWER NAME]. Last updated: October 2026. Cybersecurity News editorial is independent; no paid placement; scores are research-based, not lab-tested. Read next on Cybersecurity News: •  Top 10 Best Data Discovery Tools •  Top 9 Best Data Classification Tools •  Top 10 Best DSPM Tools •  Top 10 Best IGA Tools •  Top 10 Best JIT Access Tools • Top 10 Best PAM Tools •  Top 10 Best Database Security Tools •  Top 10 Best DLP Software • Top 10 Best Insider Threat Detection Tools •  Top 10 Best Data Masking Tools • Top 10 Best Identity Management Solutions The post Top 10 Best Data Access Governance Tools in 2026 [Ranked & Scored] appeared first on Cyber Security News .

Gertrude reposted

Kali Linux 2026.3 Released With 6 New Penetration Testing Tools and Linux Kernel 7.1

cybersecuritynews.comKali Linux 2026.3 Released With 6 New Penetration Testing Tools and Linux Kernel 7.1Kali Linux 2026.3 has been released as the third Kali update of 2026, bringing six new penetration testing tools, Linux kernel 7.1.5, KDE Plasma 6.7, refreshed image-building scripts, and a large set of Kali NetHunter changes. The release arrived on October 26 with 126 package updates and moves the kernel from version 6.19 to 7.1.5. The update follows June’s Kali Linux 2026.2 release , which added nine tools, changed Kali’s APT source format, and improved virtual machine boot times. It also continues the tool and mobile testing work seen in Kali Linux 2026.1 , the first major Kali update of the year. Six New Penetration Testing Tools The six new tools are available from Kali’s network repositories. Dalfox is an open-source cross-site scripting scanner built for automation and parameter checks. Katana is a crawling and spidering framework that can help researchers map web applications and find paths, files, and endpoints before deeper testing. Qsreplace takes URLs from standard input and replaces query string values with a chosen value, which makes it useful for preparing URL lists for repeatable web tests. Rustscan is a fast port scanner written in Rust. It can scan large port ranges and pass discovered ports to Nmap for deeper service checks. SDRangel is a Qt-based software-defined radio front end that supports devices such as RTL-SDR, BladeRF, and HackRF, giving wireless researchers a visual tool for receiving, sending, and studying radio signals. Tool Main purpose Key use Dalfox Automated XSS scanner Finds and verifies cross-site scripting flaws by testing web parameters. Katana Web crawling and spidering Maps websites, parses JavaScript, finds endpoints, and supports standard or headless crawling. Qsreplace Query-string replacement Reads URLs from standard input and replaces their query values for repeatable web security tests. Rustscan Fast network port scanner Finds open ports quickly and can pass the results to Nmap for deeper checks. SDRangel Software-defined radio interface Provides a graphical front end for radio devices such as RTL-SDR, BladeRF, and HackRF. Snaffler-ng SMB data scanner Searches readable Windows SMB shares for exposed credentials and sensitive files. Snaffler-ng searches readable Windows SMB shares for credentials and sensitive data. It supports NTLM and Kerberos sign-in, DFS discovery, archive checks, built-in classification rules, SQLite resume support, and several output formats. These additions cover web discovery, XSS testing, URL processing, port scanning, radio research, and file-share review. Like any security tool, they should only be used on systems that the tester owns or has clear permission to assess. Linux Kernel 7.1.5 and Package Updates Kali 2026.3 contains 126 package updates and moves the main Kali kernel from 6.19 to 7.1.5. Kali’s package tracker lists 7.1.5-1kali1 for the rolling branch, confirming the kernel used by the new release. The newer kernel matters because it provides the base for hardware support, drivers, system calls, and security fixes used by the rest of the distribution. Users should still test wireless adapters, graphics drivers, virtualization tools, and any custom kernel modules before relying on the update during live security work. One of the largest changes is the refresh of Kali’s public build scripts. These are the same scripts the project uses to create the official images offered through its download site. The refreshed scripts now have a more consistent structure, layout, command-line options, features, and output across supported platforms. Each refreshed project includes a build-in-container.sh script. It detects whether Docker or Podman is present, creates a build container, and runs the image build inside that container. This removes the earlier need to build Kali on a Kali system and makes the process easier to repeat on other Debian-based hosts. Kali has also improved its related build documentation. Users who want to build a standard installer can clone the kali-installer build repository, install the required packages, and run sudo ./build.sh . The default command creates a Kali rolling installer for AMD64. Builders can change the hostname, add packages such as Rustscan, select kali-dev , choose a netinst image, or target ARM64 through command-line options. Podman users can instead install Podman and run sudo ./build-in-container.sh . The work is not finished. Kali says some build scripts did not make the 2026.3 deadline, and the remaining refresh is planned for Kali 2026.4. Later stages are expected to focus on automated builds, workflows, example setups, and deeper customization. Teams with CI jobs based on the older scripts should review their pipelines because changes made during the refresh may have broken older workflows. KDE Plasma 6.7 and New Icons The optional KDE desktop has been updated to Plasma 6.7. A key feature is per-screen virtual desktops, which lets users change the workspace on one monitor without changing every display. This can be useful when keeping Burp Suite on one screen, terminals on another, and notes or documentation on a third. Plasma’s Overview also supports faster desktop switching by scrolling or using Page Up and Page Down. KDE Plasma 6.7 adds more Wayland protocol and portal support, better performance and lower power use for integrated Intel graphics, CPU-rendered applications, and setups with many full-screen windows. Network connections can be duplicated, while System Monitor, software management, printing, background application display, microphone testing, and desktop search controls also receive changes. KDE has added a light and dark theme switch, improved Breeze, restored the Oxygen and Air styles, and introduced an early preview of its Union theming system. Kali has also added icons to tools that did not have them and updated older icons so applications are easier to identify in the menu and on the Kali tools website. Xfce remains Kali’s default desktop even though KDE received the main desktop version change in this release. Major Kali NetHunter Changes Kali NetHunter, the project’s Android and wearable security testing platform, receives some of the release’s most unusual changes. The team addressed compatibility problems between modern systemd and udev components and older mobile kernels without requiring large sets of patches. Wardriving is now supported on the TicWatch Pro 3 series. An updated libnexmonkali library enables internal Wi-Fi monitor mode on the watch, allowing compatible tools inside the Kali chroot, including Aircrack-ng and Kismet, to work with the watch’s wireless hardware. Kali’s TicWatch guide says all Pro 3 GPS, LTE, Ultra GPS, and Ultra LTE variants are supported, though installation requires bootloader, recovery, operating system, root, and NetHunter changes. WearHunter is a new experimental feature that lets a user control a NetHunter watch from a phone through ADB over Wi-Fi or Bluetooth. It can run commands and install applications, with more functions planned. NFC Arsenal now provides NFC access to the Kali chroot and can read, clone, and edit Mifare Classic cards without an external adapter. The release also adds KernelSU support, allowing a generated installer ZIP to be installed through the KernelSU application when used with a patched kernel. Other NetHunter work includes a fix for TicWatch Pro 3 reboot problems and early support for devices that do not use a ramdisk. Bluetooth Arsenal’s airplane mode has returned. EvilTwin and Wardriving are easier to start, while custom commands now support Nexmon monitor mode and Wifite. Kali also fixed a crash caused by the NetHunter application’s storage request and delivered other bug fixes and speed improvements. Nine new device kernels were added. They cover Google Pixel on LineageOS 22.2 with Android 15, Huawei P9 on EMUI 8 or LineageOS 16, LG K20 Plus on LineageOS 14.1, Moto G Stylus 5G 2022 on LineageOS 23.2, Nubia Z17 on LineageOS 22.2, POCO X5 5G and Redmi Note 12 5G on crDroid 12, Redmi Note 5 Pro on LineageOS 18.1, Sony Xperia 10 V on LineageOS 23.2, and Ulefone Armor 34+ on Android 16. The release announcement also highlighted the Wardriver Project, a 2021 Honda Civic Type R shown at the Cars and Cops event in Altus, Oklahoma. The project was used to show how vehicle culture, wireless research, and cybersecurity can meet in a single build. Website and Documentation Updates Kali has applied the category layout and icons introduced in its desktop menu to kali.org/tools . Users who prefer the older short view can still open the Top 100 tools page. The documentation set gains three new pages. They explain how to extract and squash vendor firmware for mainline Linux, import a pre-made Kali QEMU virtual machine, and use NetHunter EvilTwin. Nine existing guides were updated, covering Live USB persistence, graphics problems on bare-metal systems, NetHunter on the TicWatch Pro 3, Kali as a UTM guest, the Xfce FAQ, Kali NetHunter, Raspberry Pi full-disk encryption, setting up a Kali mirror, and SSH configuration. The release cycle also added four European mirrors. Two are in the Netherlands at mirror.hacker.nl and mirror.netone.nl . Portugal gained mirror.randhost.com , while Switzerland gained kalimirror.velden.media . Kali’s mirror system can direct users to a nearby current server, but its documentation warns against adding extra repositories to the Kali source configuration because mixing repositories can break an installation. Kali also thanked community members who worked on documentation, tool pages, NetHunter, and package maintenance. The long contributor list reflects how much of the mobile kernel, device, documentation, and packaging work comes from outside contributors rather than only the core Kali team. Downloading and Upgrading Kali 2026.3 New users can obtain tested installer, live, virtual machine, ARM, cloud, container, and NetHunter images from the official Kali download page . Kali recommends the latest point-release image for most users. Weekly images contain newer packages and can reduce the number of updates needed after installation, but they are automated and do not receive the same quality checks as standard point-release images. Existing rolling users should first confirm that /etc/apt/sources.list.d/kali.sources points to the official kali-rolling repository with the main , contrib , non-free , and non-free-firmware components. They can then run sudo apt update followed by sudo apt full-upgrade -y . If the system marks a reboot as required, users should restart before checking the result. The installed release can be checked with grep VERSION /etc/os-release , which should show 2026.3 . The active kernel can be checked with uname -r , with the AMD64 release example showing 7.1.5+kali-amd64 . The exact kernel string can differ by architecture. Kali’s update guidance recommends checking for updates every few days or weeks, or sooner when a required tool or security fix is released. It also advises testing all needed tools before a planned security engagement and avoiding updates during active work because a rolling package change can sometimes break a tool at the wrong time Update defenses against new malware as soon as it appears. Integrate TI Feeds with data from 16K SOCs . The post Kali Linux 2026.3 Released With 6 New Penetration Testing Tools and Linux Kernel 7.1 appeared first on Cyber Security News .

Gertrude reposted

Gertrude reposted

India’s Film Sensor Board Data Breach – Unreleased Scripts, 500+ Film Titles Exposed

cybersecuritynews.comIndia’s Film Sensor Board Data Breach – Unreleased Scripts, 500+ Film Titles ExposedIndia’s Central Board of Film Certification (CBFC) is investigating a reported data breach involving confidential documents linked to more than 500 film titles. The exposed records reportedly include shooting scripts, censor cut orders, certification files and private distribution agreements submitted through its e-Cinepramaan portal. The Hindu first reported the exposure, which involved film certification applications rather than leaked movie files. Its reporting describes more than 500 affected titles, including dozens of feature films. That distinction matters because the incident does not mean 500 complete films or 500 separate scripts were stolen. Film Scripts and Business Records Exposed Filmmakers use e-Cinepramaan to submit documents needed for certification before theatrical release. According to reports, the files were allegedly accessed through this portal and remained available online for several days before removal. The material reportedly appeared on the Internet Archive, where it could be downloaded. Documents dated from December 2025 to August 2026 were among the exposed records, according to Digit’s coverage of the findings. The commercial impact could extend beyond spoilers. Local distribution agreements for The Secret Agent and Good Luck, Have Fun, Don’t Die were reportedly included. At least three agreements disclosed licensing fees, potentially revealing private deal terms to competitors or future negotiating partners. For unreleased productions, exposed scripts could reveal storylines before marketing campaigns begin. Cut orders could also disclose scenes removed during certification. These are potential consequences of the reported exposure, not confirmed cases of financial loss or misuse. The CBFC has reportedly started an investigation and a security audit. The board said its initial checks had not found evidence of further access to the documents identified in the report. It also said there was no indication that individual filmmakers’ accounts had been compromised. According to India Today’s coverage , uploads stopped after the portal became unavailable for several hours on October 4. That timing alone does not establish how access occurred or whether the outage stopped it. The Internet Archive reportedly removed the account involved. Cybercrime authorities received a complaint, and the Indian Computer Emergency Response Team, CERT-In, was notified. The investigation has not yet established the full exposure. The available reporting does not identify a confirmed software flaw or access method. Cyber Security News previously covered an Indian Post Office portal document exposure involving broken access controls, but there is no evidence linking that weakness to CBFC. Similarly, its SBI data breach coverage separated exposed records from an unconfirmed entry point. For CBFC, the key unanswered questions remain how documents became accessible, which submissions were affected, and whether copies remain elsewhere. Until investigators publish findings, claims of stolen passwords, ransomware or a specific vulnerability remain unsupported by the available public reporting. Update defenses against new malware as soon as it appears. Integrate TI Feeds with data from 16K SOCs . The post India’s Film Sensor Board Data Breach – Unreleased Scripts, 500+ Film Titles Exposed appeared first on Cyber Security News .

Gertrude reposted

HTTP2Shell Vulnerability Extends Beyond HTTP, Affecting .NET, FFmpeg, ClickHouse, and Apache Arrow

cybersecuritynews.comHTTP2Shell Vulnerability Extends Beyond HTTP, Affecting .NET, FFmpeg, ClickHouse, and Apache ArrowThe HTTP2Shell vulnerability reaches beyond web traffic, with new research showing how the same Brotli decoder flaw (CVE-2026-111497) can disrupt .NET applications, FFmpeg media processing, ClickHouse servers, and Apache Arrow workloads. The findings show that checking Node.js versions alone can leave other exposed software unnoticed. In research published on October 25, JFrog researchers Aviv Engelberg, Eddy Tsalolikhin, and Ofri Ouzan traced CVE-2026-111497 through several software stacks. Their findings describe crashes, memory corruption, and an endless decoding loop, depending on how each application uses the affected library. First disclosed in Node.js security updates on October 21, the vulnerability sits in Google’s Brotli decoder rather than HTTP itself. An invalid block switch can be mistaken for a request for more input. Processing then continues with broken decoder state, allowing a write beyond the intended memory buffer. Affected upstream releases include Brotli 1.0.3 through versions before 1.0.10, 1.1.0 before 1.1.1, and 1.2.0 before 1.2.1. Projects may apply the fix without changing to these upstream versions, so teams must check vendor patch records rather than relying on version numbers alone. HTTP2Shell Vulnerability In FFmpeg, researchers reached the decoder through libjxl, which processes JPEG XL images. A crafted image carried malformed Brotli data inside a compressed metadata box. When libjxl decoded that data, memory corruption caused a crash during cleanup. The test showed attacker control over a corrupted pointer value. However, it did not establish a complete remote code execution exploit for FFmpeg. This file-based route adds to concerns covered in earlier reporting on FFmpeg media-file vulnerabilities and other FFmpeg memory-corruption flaws . Those reports concern separate vulnerabilities. JFrog also triggered a native crash through .NET’s Brotli decompression APIs. A two-stage stream left the decoder in an invalid state before a memory operation moved outside valid heap data. Unlike a normal managed exception, the resulting segmentation fault terminated the process. The demonstration used a local console application. However, related decoder paths can serve HttpClient response decompression and ASP.NET Core request-decompression middleware. Microsoft announced on October 25 that it was rolling out updates for supported runtimes and SDKs. ClickHouse failed after receiving one crafted HTTP request with a 23 MB Brotli-compressed body. Decoder corruption caused a crash during cleanup, stopping the tested server and interrupting active queries. JFrog reported that a fix had been merged, but no patched release had shipped when its research appeared. Apache Arrow showed a different failure. A 534-byte input sent through pyarrow’s Brotli decoding path caused an endless loop that consumed CPU and blocked completion. Brotli 1.2.1 rejected the same input in under a second. Arrow’s tracking issue remained open at publication. According to the Sysdig Threat Research Team , Node.js fixes were released in versions 22.23.4, 24.22.1, and 26.12.1, with the 24.22.1 release notes confirming the Brotli patch. Other applications require their own updated builds or library packages. Teams should trace untrusted files, buffers, requests, and responses into decompression code. JFrog’s scanner helps identify potential paths, but a match alone does not prove remote exploitability. Update defenses against new malware as soon as it appears. Integrate TI Feeds with data from 16K SOCs . The post HTTP2Shell Vulnerability Extends Beyond HTTP, Affecting .NET, FFmpeg, ClickHouse, and Apache Arrow appeared first on Cyber Security News .

Gertrude reposted

Microsoft Authenticator Flaw Lets Malicious Android Apps Steal Account Tokens With Zero Permissions

cybersecuritynews.comMicrosoft Authenticator Flaw Lets Malicious Android Apps Steal Account Tokens With Zero PermissionsMicrosoft patched high-severity flaw CVE-2026-80097 (CVSS 8.6) in Authenticator for Android, allowing malicious apps with no declared permissions to steal work account access tokens due to improper authentication in its broker component. Microsoft classified the flaw as a local elevation-of-privilege vulnerability. The issue affected Android devices with Microsoft Authenticator installed and a signed-in work account. Enclave researchers found that an untrusted app could pretend to be a trusted Microsoft application, such as Microsoft Teams, and ask Authenticator to issue delegated tokens for that identity. The request did not need user approval, account credentials, or Android permissions beyond being installed on the device. At the center of the bug was an exported Android activity named com.microsoft.identity.client.AccountChooserActivity. Other apps can start exported activities on the same device. In this case, the activity accepted a broker request from the calling app. It returned the authentication result after processing it. The key problem was how Authenticator verified the requesting application. The broker request included the claimed app package name, client ID, redirect URI, requested scopes, and even a caller UID value. Microsoft Authenticator Flaw Enclave researchers reported that the malicious application could supply these fields rather than having them tied to the app that actually launched the request. Authenticator did perform a signature-related redirect URI validation. However, the check focused on the app identity claimed in the request. If the attacker claimed to be Teams, the vulnerable logic checked whether the redirect URI matched the real installed Teams package. Because Teams was legitimately installed, the attacker could build a valid redirect URI from its public package signature and pass the check. In short, the app verified whether the claimed identity looked valid, but did not confirm that the real caller was the app it claimed to be. The vulnerable activity could identify the package that launched it, according to the research. However, it did not use that information to control trust. Successful requests returned token data through the activity result bundle. The tokens could include access tokens, refresh tokens, ID tokens, and client information. Depending on the impersonated Microsoft client and requested permissions, the impact could extend to Microsoft Graph resources such as mailboxes, calendars, OneDrive files, SharePoint content, and Teams-related services. The researchers demonstrated the risk by impersonating multiple Microsoft apps. A Teams identity requesting Microsoft Graph access could receive delegated permissions that let it read and write mail, send messages, access files, and modify calendars. This flaw is especially important for organizations that use Android devices to access Microsoft 365 workloads. Microsoft fixed the issue in Microsoft Authenticator for Android version 6.2606.4246, which was released in July 2026. Organizations and individual users should update the app through Google Play as soon as possible and verify that managed devices are running a current release. Microsoft’s advisory describes the issue as improper authentication that could let an unauthorized local attacker elevate privileges. The flaw also highlights why mobile identity brokers must validate the real calling application, including its package identity, UID, and signing certificate, rather than relying on app-controlled values in an intent. The incident highlights Microsoft’s ongoing efforts to protect Entra credentials on rooted Android and jailbroken iOS devices , where malware and weakened security controls increase enterprise identity risks. Organizations should review mobile application controls, enforce timely app updates through MDM or EMM platforms, and restrict sideloaded applications where possible. Security teams should also monitor unusual Microsoft Graph activity, unexpected consent behavior, and token use from unfamiliar Android devices. Microsoft’s official CVE-2026-80097 advisory should be used for ongoing remediation guidance. Update defenses against new malware as soon as it appears. Integrate TI Feeds with data from 16K SOCs . The post Microsoft Authenticator Flaw Lets Malicious Android Apps Steal Account Tokens With Zero Permissions appeared first on Cyber Security News .

Gertrude reposted

Gertrude reposted

Gertrude reposted

Hacker Exploits Critical PHP2Shell Flaws to Win $2,000 Bitcoin Challenge, Releases PoC

cybersecuritynews.comHacker Exploits Critical PHP2Shell Flaws to Win $2,000 Bitcoin Challenge, Releases PoCA security researcher known online as killa has won a public Bitcoin challenge by using two critical PHP flaws to reach a test server. The winning run took 19.28 hours. The prize pot was 0.02511679 BTC, worth $2,021.22 at the time of the win on October 25, 2026, at 15:47 UTC. The researcher then published a proof of concept (PoC) on GitHub. The challenge ran on stealmybitcoin.com. The site used unpatched PHP and held a wallet key behind a remote code execution test, which means the goal was to run commands on the server from the outside. Donations pushed the prize from $500 to more than $2,000 while the test ran. The creator said early tries failed because the server first served static files through PHP’s command-line mode, which skipped the bugs. After the site moved to a real PHP page, the test became possible. PHP2Shell Flaws Exploited The bugs are tracked as CVE-2026-109618 and CVE-2026-109619 , and the group is called PHP2Shell. Both carry a CVSS v4.0 score of 9.2, which is rated critical. The first bug can corrupt memory during cleanup after an out-of-memory condition. The second lets data left by an earlier request in a shared worker be reused by a later request. PHP released fixes on October 21, 2026, in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Google’s guidance says the affected range covers PHP 5.4 through 8.5.11. Older branches such as 8.1 and earlier no longer get official fixes, so those sites need to move to a supported version. The public script uses two memory leaks. The first leak reveals a heap address, and the second reveals a PHP code address. With both addresses, a final request places a forged structure in memory that leads PHP to call its system function. The script then prints a random test marker, the user ID, and the hash of the flag program. The write-up also shows the limits of the work. The script was built and tested against a local lab copy, not the live site, and it succeeded in about seven of ten lab runs. The author admits that the full live request was not captured. The recovered key also did not match the advertised prize address, and the author called that a mistake on the creator’s side. Public exploit code is now available , and hacking activity started before the patches. Amazon reported attempts dating back to October 17, four days before the fixes. Sophos said it blocked attempts to deliver Potassium, a likely Mirai botnet variant, but it found no proof of a successful compromise. Upgrading to a patched PHP release is the only full fix. Firewall rules and configuration changes may reduce risk, but they do not close the flaws. After upgrading, restart services and confirm that the active workers run the new build, because bundled runtimes and containers may still use old code. For more background, read our earlier coverage of the PHP2Shell vulnerability and public PoC and the PHP emergency patch release . Update defenses against new malware as soon as it appears. Integrate TI Feeds with data from 16K SOCs . The post Hacker Exploits Critical PHP2Shell Flaws to Win $2,000 Bitcoin Challenge, Releases PoC appeared first on Cyber Security News .

Spot on why the GOP sold their souls. They tell themselves it’s okay because they believe in the old way of GOP standards and this is temporary as long as they keep power. At lease I think this is why.

Bill Madden@maddenifico.bsky.social

Every. Fucking. Word.

Gertrude reposted

CONGRESS APPROVED THE MONEY — SO WHY ARE OUR TROOPS STILL LIVING LIKE THIS? Pete Hegseth owes our troops & their families an explanation. #SupportTheTroops 🧵

Gertrude reposted

Ancient Greeks built a 30-gear bronze computer over 2,000 years ago that predicted eclipses. The Antikythera mechanism was just the start of their engineering genius.

Gertrude reposted

OBAMA: "Trump is focused on enriching himself & his family/friends. A Venezuelan billionaire wanted a pardon, so he paid a Trump lawyers $50 million — and lo & behold! The pardon falls out of the sky... We’ve never seen a president straight-up grifting on your dime like this."

Spot on. AI is not just the only problem in insurance—avarice is the underlying cost.

Abdul El-Sayed@abdulelsayed.bsky.social

The only Planned Parenthood in the UP closed in 2025. Medicare for All means access to medical care for all, in every corner of the country.