A U.S. court denied Apple a stay on a ruling that requires the company to stop charging developers for payments made outside the App Store through links in apps.

Japan-based Ispace confirmed its Resilience lander likely crashed during its second failed attempt at a lunar landing, after a sensor malfunction prevented proper deceleration. Despite the setback, the company remains committed to future missions, with funding secured for a third attempt using a new lander, Apex 1.0, scheduled for 2027. "Until then, Ispace has its work cut out for it," reports CNN. "[Ispace CEO and founder Takeshi Hakamada] said during the news briefing he will need to work to regain the trust of investors, and the company will need to deeply investigate what went wrong on the Resilience mission to ensure similar issues don't plague Apex 1.0." The company has ambitious "plans to eventually build a city on the lunar surface that would house a thousand people and welcome thousands more for tourist visits," notes ABC News. "If ispace is going to establish a colony on the moon, it will need to identify an ample supply of ice or water, which it will convert into fuel for a future lunar fueling station. The ability to produce fuel on the moon will enable the company to transport people back and forth between the Earth and the moon." Read more of this story at Slashdot.

Email authentication protocols like SPF, DKIM, and DMARC play a critical role in protecting domains from spoofing and phishing. However, when SEGs are introduced into the email path, the interaction with these protocols becomes more complex. Security gateways(SEGs) are a core part of many organizations’ email infrastructure. They act as intermediaries between the public internet and internal mail systems, inspecting, filtering, and routing messages. This blog examines how security gateways handle SPF, DKIM, and DMARC, with real-world examples from popular gateways such as Proofpoint, Mimecast, and Avanan. We’ll also cover best practices for maintaining authentication integrity and avoiding misconfigurations that can compromise email authentication or lead to false DMARC failures. Security gateways often sit at the boundary between your organization and the internet, managing both inbound and outbound email traffic. Their role affects how email authentication protocols behave. An inbound SEG examines emails coming into your organization. It checks SPF, DKIM, and DMARC to determine if the message is authentic and safe before passing it to your internal mail servers. An outbound SEG handles emails sent from your domain. It may modify headers, rewrite envelope addresses, or even apply DKIM signing. All of these can impact SPF,  DKIM, or DMARC validation on the recipient’s side. Understanding how SEGs influence these flows is crucial to maintaining proper authentication and avoiding unexpected DMARC failures. Inbound Handling of SPF, DKIM, and DMARC by Common Security Gateways When an email comes into your organization, your security gateway is the first to inspect it. It checks whether the message is real, trustworthy, and properly authenticated. Let’s look at how different SEGs handle these checks. Avanan (by Check Point) SPF: Avanan verifies whether the sending server is authorized to send emails for the domain by checking the SPF record. DKIM: It verifies if the message was signed by the sending domain and if that signature is valid. DMARC: It uses the results of the SPF and DKIM check to evaluate DMARC. However, final enforcement usually depends on how DMARC is handled by Microsoft 365 or Gmail, as Avanan integrates directly with them. Avanan offers two methods of integration:1. API integration: Avanan connects via APIs, no change in MX, usually Monitor or Detect modes.2. Inline integration: Avanan is placed inline in the mail flow (MX records changed), actively blocking or remediating threats. Proofpoint Email Protection SPF: Proofpoint checks SPF to confirm the sender’s IP is authorized to send on behalf of the domain. You can set custom rules (e.g. treat “softfail” as “fail”). DKIM: It verifies DKIM signatures and shows clear pass/fail results in logs. DMARC: It fully evaluates DMARC by combining SPF and DKIM results with alignment checks. Administrators can configure how to handle messages that fail DMARC, such as rejecting, quarantining, or delivering them. Additionally, Proofpoint allows whitelisting specific senders you trust, even if their emails fail authentication checks. Integration Methods Inline Mode: In this traditional deployment, Proofpoint is positioned directly in the email flow by modifying MX records. Emails are routed through Proofpoint’s infrastructure, allowing it to inspect and filter messages before they reach the recipient’s inbox. This mode provides pre-delivery protection and is commonly used in on-premises or hybrid environments. API-Based (Integrated Cloud Email Security – ICES) Mode: Proofpoint offers API-based integration, particularly with cloud email platforms like Microsoft 365 and Google Workspace. In this mode, Proofpoint connects to the email platform via APIs, enabling it to monitor and remediate threats post-delivery without altering the email flow. This approach allows for rapid deployment and seamless integration with existing cloud email services. Mimecast SPF: Mimecast performs SPF checks to verify whether the sending server is authorized by the domain’s SPF record. Administrators can configure actions for SPF failures, including block, quarantine, permit, or tag with a warning. This gives flexibility in balancing security with business needs. DKIM: It validates DKIM signatures by checking that the message was correctly signed by the sending domain and that the content hasn’t been tampered with. If the signature fails, Mimecast can take actions based on your configured policies. DMARC: It fully evaluates DMARC by combining the results of SPF and DKIM with domain alignment checks. You can choose to honor the sending domain’s DMARC policy (none, quarantine, reject) or apply custom rules, for example, quarantining or tagging messages that fail DMARC regardless of the published policy. This allows more granular control for businesses that want to override external domain policies based on specific contexts. Integration Methods Inline Deployment: Mimecast is typically deployed as a cloud-based secure email gateway. Organizations update their domain’s MX records to point to Mimecast, so all inbound (and optionally outbound) emails pass through it first. This allows Mimecast to inspect, filter, and process emails before delivery, providing robust protection. API Integrations: Mimecast also offers API-based services through its Mimecast API platform, primarily for management, archival, continuity, and threat intelligence purposes. However, API-only email protection is not Mimecast’s core model. Instead, the APIs are used to enhance the inline deployment, not replace it. Barracuda Email Security Gateway SPF: Barracuda checks the sender’s IP against the domain’s published SPF record. If the check fails, you can configure the system to block, quarantine, tag, or allow the message, depending on your policy preferences. DKIM: It validates whether the incoming message includes a valid DKIM signature. The outcome is logged and used to inform further policy decisions or DMARC evaluations. DMARC: It combines SPF and DKIM results, checks for domain alignment, and applies the DMARC policy defined by the sender. Administrators can also choose to override the DMARC policy, allowing messages to pass or be treated differently based on organizational needs (e.g., trusted senders or internal exceptions). Integration Methods Inline mode (more common and straightforward): Barracuda Email Security Gateway is commonly deployed inline by updating your domain’s MX records to point to Barracuda’s cloud or on-premises gateway. This ensures that all inbound emails pass through Barracuda first for filtering and SPF, DKIM, and DMARC validation before being delivered to your mail servers. Deployment Behind the Corporate Firewall: Alternatively, Barracuda can be deployed in transparent or bridge mode without modifying MX records. In this setup, the gateway is placed inline at the network level, such as behind a firewall, and intercepts mail traffic transparently. This method is typically used in complex on-premises environments where changing DNS records is not feasible. Cisco Secure Email (formerly IronPort) Cisco Secure Email acts as an inline gateway for inbound email, usually requiring your domain’s MX records to point to the Cisco Email Security Appliance or cloud service. SPF: Cisco Secure Email verifies whether the sending server is authorized in the sender domain’s SPF record. Administrators can set detailed policies on how to handle SPF failures. DKIM: It validates the DKIM signature on incoming emails and logs whether the signature is valid or has failed. DMARC: It evaluates DMARC by combining SPF and DKIM results along with domain alignment checks. Admins can configure specific actions, such as quarantine, reject, or tag, based on different failure scenarios or trusted sender exceptions. Integration methods On-premises Email Security Appliance (ESA): You deploy Cisco’s hardware or virtual appliance inline, updating MX records to route mail through it for filtering. Cisco Cloud Email Security: Cisco offers a cloud-based email security service where MX records are pointed to Cisco’s cloud infrastructure, which filters and processes inbound mail. Cisco Secure Email also offers advanced, rule-based filtering capabilities and integrates with Cisco’s broader threat protection ecosystem, enabling comprehensive inbound email security. Outbound Handling of SPF, DKIM, and DMARC by Common Security Gateways When your organization sends emails, security gateways can play an active role in processing and authenticating those messages. Depending on the configuration, a gateway might rewrite headers, re-sign messages, or route them through different IPs – all actions that can help or hurt the authentication process. Let’s look at how major SEGs handle outbound email flow. Avanan – Outbound Handling and Integration Methods Outbound Logic Avanan analyzes outbound emails primarily to detect data loss, malware, and policy violations. In API-based integration, emails are sent directly by the original mail server (e.g., Microsoft 365 or Google Workspace), so SPF and DKIM signatures remain intact. Avanan does not alter the message or reroute traffic, which helps maintain full DMARC alignment and domain reputation. Integration Methods 1. API Integration: Connects to Microsoft 365 or Google Workspace via API. No MX changes are needed. Emails are scanned after they are sent, with no modification to SPF, DKIM, or the delivery path.  How it works: Microsoft Graph API or Google Workspace APIs are used to monitor and intervene in outbound emails. Protection level: Despite no MX changes, it can offer inline-like protection, meaning it can block, quarantine, or encrypt emails before they are delivered externally. SPF/DKIM/DMARC impact: Preserves original headers and signatures since mail is sent directly from Microsoft/Google servers. 2. Inline Integration: Requires changing MX records to route email through Avanan. In this mode, Avanan can intercept and inspect outbound emails before delivery. Depending on the configuration, this may affect SPF or DKIM if not properly handled. How it works: Requires adding Avanan’s Protection level: Traditional inline security with full visibility and control, including encryption, DLP, policy enforcement, and advanced threat protection. SPF/DKIM/DMARC impact: SPF configuration is needed by adding Avanan’s include mechanism to the sending domain’s SPF record. The DKIM record of the original sending source is preserved. For configurations, you can refer to the steps in this blog. Proofpoint – Outbound Handling and Integration Methods Outbound Logic Proofpoint analyzes outbound emails to detect and prevent data loss (DLP), to identify advanced threats (malware, phishing, BEC) originating from compromised internal accounts, and to ensure compliance. Their API integration provides crucial visibility and powerful remediation capabilities, while their traditional gateway (MX record) deployment delivers true inline, pre-delivery blocking for outbound traffic. Integration methods 1. API Integration: No MX record changes are required for this deployment method. Integration is done with Microsoft 365 or Google Workspace. How it works: Through its API integration, Proofpoint gains deep visibility into outbound emails and provides layered security and response features, including: Detect and alert: Identifies sensitive content (Data Loss Prevention violations), malicious attachments, or suspicious links in outbound emails. Post-delivery remediation (TRAP): A key capability of the API model is Threat Response Auto-Pull (TRAP), which enables Proofpoint to automatically recall, quarantine, or delete emails after delivery. This is particularly useful for internally sent messages or those forwarded to other users. Enhanced visibility: Aggregates message metadata and logs into Proofpoint’s threat intelligence platform, giving security teams a centralized view of outbound risks and user behavior. Protection level: API-based integration provides strong post-delivery detection and response, as well as visibility into DLP incidents and suspicious behavior.  SPF/DKIM/DMARC impact: Proofpoint does not alter SPF, DKIM, or DMARC because emails are sent directly through Microsoft or Google servers. Since Proofpoint’s servers are not involved in the actual sending process, the original authentication headers remain intact. 2. Gateway Integration (MX Record/Smart Host): This method requires updating MX records or routing outbound mail through Proofpoint via a smart host. How it works: Proofpoint acts as an inline gateway, inspecting emails before delivery. Inbound mail is filtered via MX changes; outbound mail is relayed through Proofpoint’s servers. Threat and DLP filtering: Scans outbound messages for sensitive content, malware, and policy violations. Real-time enforcement: Blocks, encrypts, or quarantines emails before they’re delivered. Policy controls: Applies rules based on content, recipient, or behavior. Protection level: Provides strong, real-time protection for outbound traffic with pre-delivery enforcement, DLP, and encryption. SPF/DKIM/DMARC impact: Proofpoint becomes the sending server: SPF: You need to configure ProofPoint’s SPF. DKIM: Can sign messages; requires DKIM setup. DMARC: DMARC passes if SPF and DKIM are set up properly. Please refer to this article to configure SPF and DKIM for ProofPoint. Mimecast – Outbound Handling and Integration Methods Outbound Logic Mimecast inspects outbound emails to prevent data loss (DLP), detect internal threats such as malware and impersonation, and ensure regulatory compliance. It primarily functions as a Secure Email Gateway (SEG), meaning it sits directly in the outbound email flow. While Mimecast offers APIs, its core outbound protection is built around this inline gateway model. Integration Methods 1. Gateway Integration (MX Record change required) This is Mimecast’s primary method for outbound email protection. Organizations route their outbound traffic through Mimecast by configuring their email server (e.g., Microsoft 365, Google Workspace, etc.) to use Mimecast as a smart host. This enables Mimecast to inspect and enforce policies on all outgoing emails in real time. How it works: Updating outbound routing in your email system (smart host settings), or Using Mimecast SMTP relay to direct messages through their infrastructure. Mimecast then scans, filters, and applies policies before the email reaches the final recipient. Protection level: Advanced DLP: Identifies and prevents sensitive data leaks. Impersonation and Threat Protection: Blocks malware, phishing, and abuse from compromised internal accounts. Email Encryption and Secure Messaging: Applies encryption policies or routes messages via secure portals. Regulatory Compliance: Enforces outbound compliance rules based on content, recipient, or metadata. SPF/DKIM/DMARC impact: SPF: Your SPF record must include Mimecast’s SPF mechanism based on your region to avoid SPF failures. DKIM: A new DKIM record should be configured to make sure your emails are DKIM signed when routing through Mimecast. DMARC: With correct SPF and DKIM setup, Mimecast ensures DMARC alignment, maintaining your domain’s sending reputation. Please refer to the steps in this detailed article to set up SPF and DKIM for Mimecast. 2. API Integration (Complementary to Gateway) Mimecast’s APIs complement the main gateway by providing automation, reporting, and management tools rather than handling live outbound mail flow. They allow you to manage policies, export logs, search archived emails, and sync users. APIs enhance visibility and operational tasks but do not provide real-time filtering or blocking of outbound messages. Since APIs don’t process live mail, they have no direct effect on SPF, DKIM, or DMARC; those depend on your gateway (smart host) setup. Barracuda – Outbound Handling and Integration Methods Outbound Logic Barracuda analyzes outbound emails to prevent data loss (DLP), block malware, stop phishing/impersonation attempts from compromised internal accounts, and ensure compliance. Barracuda offers flexible deployment options, including both traditional gateway (MX record) and API-based integrations. While both contribute to outbound security, their roles are distinct. Integration Methods 1. Gateway Integration (MX Record / Smart Host) — Primary Inline Security How it works: All outbound emails pass through Barracuda’s security stack for real-time inspection, threat blocking, and policy enforcement before delivery. Protection level: Comprehensive DLP (blocking, encrypting, or quarantining sensitive content)  Outbound spam and virus filtering  Enforcement of compliance and content policies This approach offers a high level of control and immediate threat mitigation on outbound mail flow. SPF/DKIM/DMARC impact: SPF: Update SPF records to include Barracuda’s sending IPs or SPF include mechanism. DKIM: Currently, no explicit setup is needed; DKIM of the main sending source is preserved. Refer to this article for more comprehensive guidance on Barracuda SEG configuration. 2. API Integration (Complementary & Advanced Threat Focus) How it works: The API accesses cloud email environments to analyze historical and real-time data, learning normal communication patterns to detect anomalies in outbound emails. It also supports post-delivery remediation, enabling the removal of malicious emails from internal mailboxes after sending. Protection level: Advanced AI-driven detection and near real-time blocking of outbound threats, plus strong post-delivery cleanup capabilities. SPF/DKIM/DMARC impact: Since mail is sent directly by the original mail server (e.g., Microsoft 365), SPF and DKIM signatures remain intact, preserving DMARC alignment and domain reputation. Cisco Secure Email (formerly IronPort) – Outbound Handling and Integration Methods Outbound Logic Cisco Secure Email protects outbound email by preventing data loss (DLP), blocking spam and malware from internal accounts, stopping business email compromise (BEC) and impersonation attacks, and ensuring compliance. Cisco provides both traditional gateway appliances/cloud gateways and modern API-based solutions for layered outbound security. Integration Methods 1. Gateway Integration (MX Record / Smart Host) – Cisco Secure Email Gateway (ESA) How it works: Organizations update MX records to route mail through the Cisco Secure Email Gateway or configure their mail server (e.g., Microsoft 365, Exchange) to smart host outbound email via the gateway. All outbound mail is inspected and policies enforced before delivery. Protection level: Granular DLP (blocking, encrypting, quarantining sensitive content) Outbound spam and malware filtering to protect IP reputation Email encryption for sensitive outbound messages Comprehensive content and attachment policy enforcement SPF: Check this article for comprehensive guidance on Cisco SPF settings. DKIM: Refer to this article for detailed guidance on Cisco DKIM settings. 2. API Integration – Cisco Secure Email Threat Defense How it works: Integrates directly via API with Microsoft 365 (and potentially Google Workspace), continuously monitoring email metadata, content, and user behavior across inbound, outbound, and internal messages. Leverages Cisco’s threat intelligence and AI to detect anomalous outbound activity linked to BEC, account takeover, and phishing. Post-Delivery Remediation: Automates the removal or quarantine of malicious or policy-violating emails from mailboxes even after sending. Protection level: Advanced, AI-driven detection of sophisticated outbound threats with real-time monitoring and automated remediation. Complements gateway filtering by adding cloud-native visibility and swift post-send action. SPF/DKIM/DMARC impact: Since emails are sent directly by the original mail server, SPF and DKIM signatures remain intact, preserving DMARC alignment and domain reputation. If you have any questions or need assistance, feel free to reach out to EasyDMARC technical support.

Photo Credit: ispace A delay in rangefinder data prevented timely deceleration, causing a hard landing on the lunar surface Highlights Resilience lander lost signal one minute before scheduled moon touchdown Delayed laser rangefinder data caused failure in the landing speed adjust ispace lunar lander crashes on final descent, marking its second mission Advertisement A Japanese spacecraft attempting to achieve the country's first private moon landing instead crashed on the lunar surface, according to mission officials. The Resilience lander, developed by Tokyo-based ispace, lost communication one minute and 45 seconds before its scheduled soft touchdown on June 5 at 3:17 p.m. EDT. The descent was targeted for the Mare Frigoris region on the Moon's near side. ispace had its second problem on the moon when its laser rangefinder broke, which is a big improvement over its prior failure in April 2023.Japan's Resilience Lunar Lander Crashes in Hard Landing, ispace Vows to Learn and RebuildAs per an official statement from ispace, telemetry from Resilience revealed that the rangefinder's delayed data caused a failure in adjusting landing speed. This likely led to a “hard landing”, suggesting the spacecraft hit the moon's surface too fast to survive or complete its mission. The lander, carrying five payloads, such as a Tenacious rover and scientific instruments, crashed with no survivors. The firm's CEO, Takeshi Hakamada, apologised and remarked that the company would use the mission to learn about future missions.The Hakuto-R Mission 2 team launched a 7.5-foot-tall, 2,200-pound Resilience lander into space aboard a SpaceX Falcon 9 rocket in early May. But with a perfect orbit, the lander smashed into the lunar surface at 192 metres – an echo of Mission 1's mission failure in 2023, which crashed because a fault in one of its altitude sensors was not corrected.The Resilience crash adds to private attempts to explore the moon, including the unsuccessful Beresheet and Peregrine missions. Crewed landings such as Odysseus and Blue Ghost prove that dreams of commercial space are possible. The second Hakuto-R mission was a private attempt and a blow to Japan's space ambitions. Failure has not stopped ispace development for Mission 3 and Mission 4 with its larger Apex 1.0 lander.Hakamada mentioned that the priority for the team was now to find out what caused the crash. “Supporters are disappointed,” CFO Nozaki says, “but ispace has yet to cover the moon, and the road does not end, even if Mission 2 didn't go as planned.” For the latest tech news and reviews, follow Gadgets 360 on X, Facebook, WhatsApp, Threads and Google News. For the latest videos on gadgets and tech, subscribe to our YouTube channel. If you want to know everything about top influencers, follow our in-house Who'sThat360 on Instagram and YouTube. Further reading: ispace, Hakuto-R, moon landing, Resilience, lunar exploration Gadgets 360 Staff The resident bot. If you email me, a human will respond. More Related Stories

News Space A private Japanese spacecraft failed on its way to the moon’s surface  A lost signal marks the second imperfect attempt at a lunar landing for Tokyo-based company ispace The Resilience lunar lander (illustrated, left), owned by Tokyo-based company ispace, attempted to touch down on the moon’s surface on June 5. The spacecraft contains several payloads, including a micro rover called Tenacious (right). ispace By McKenzie Prillaman 6 hours ago A Japanese lunar lander called Resilience failed to softly touch down on the moon’s surface on June 5. The spacecraft’s status is currently unknown after Tokyo-based company ispace lost communication with it, but the lander was unable to decelerate properly. The company is calling it quits on the current mission. “This is our second failure, and by these results, we have to really take it seriously,” ispace founder and CEO Takeshi Hakamada said during a June 5 press briefing. “We have to do some analysis to find out what caused” the problems. Sign up for our newsletter We summarize the week's scientific breakthroughs every Thursday.

A significant cyber breach at His Majesty’s Revenue and Customs (HMRC) that saw scammers cheat the public purse out of approximately £47m has been met with dismay from security experts thanks to the sheer simplicity of the attack, which originated via account takeover attempts on legitimate taxpayers. HMRC disclosed the breach to a Treasury Select Committee this week, revealing that hackers accessed the online accounts of about 100,000 people via phishing attacks and managed to claim a significant amount of money in tax rebates before being stopped. It is understood that those individuals affected have been contacted by HMRC – they have not personally lost any money and are not themselves in any trouble. Arrests in the case have already been made. During proceedings, HMRC also came in for criticism by the committee’s chair Meg Hillier, who had learned about the via an earlier news report on the matter, over the length of time taken to come clean over the incident. With phishing emails sent to unwitting taxpayers identified as the initial attack vector for the scammers, HMRC might feel relieved that it has dodged full blame for the incident. But according to Will Richmond-Coggan, a partner specialising in data and cyber disputes at law firm Freeths, even though the tax office had gone to pains to stress its own systems were never actually compromised, the incident underscored just how widespread the consequences of cyber attacks can be – snowballing from simple origins into a multimillion pound loss. “It is clear from HMRC's explanation that the crime against HMRC was only possible because of earlier data breaches and cyber attacks,” said Richmond-Coggan. “Those earlier attacks put personal data in the hands of the criminals which enabled them to impersonate tax payers and apply successfully to claim back tax.” Meanwhile, Gerasim Hovhannisyan, CEO of EasyDMARC, an email security provider, pointed out that phishing against both private individuals and businesses and other organisations had long ago moved beyond the domain of scammers chancing their luck. While this type of scattergun fraud remains a potent threat, particularly to consumers who may not be informed about cyber security matters – the scale of the HMRC phish surely suggests a targeted operation, likely using carefully crafted email purporting to represent HMRC itself, designed to lure self-assessment taxpayers into handing over their accounts. Not only that, but generative artificial intelligence (GenAI) means targeted phishing operations have become exponentially more dangerous in a very short space of time, added Hovhannisyan. “[It] has made [phishing] scalable, polished, and dangerously convincing, often indistinguishable from legitimate communication. And while many organisations have strengthened their security perimeters, email remains the most consistently exploited and underestimated attack vector,” he said. “These scams exploit human trust, using urgency, authority, and increasingly realistic impersonation tactics. If HMRC can be phished, anyone can.” Added Hovhannisyan: “What’s more alarming is that the Treasury Select Committee only learned of the breach through the news. When £47m is stolen through impersonation, institutions can’t afford to stay quiet. Delayed disclosure erodes trust, stalls response, and gives attackers room to manoeuvre.” Once again a service’s end-users have turned out to be the source of a cyber attack and as such, whether they are internal or – as in this case – external, are often considered an organisation’s first line of defence. However, it is not always wise to take this approach, and for an organisation like HMRC daily engaging with members of the public, it is also not really possible. Security education is a difficult proposition at the best of times and although the UK’s National Cyber Security Centre (NCSC) provides extensive advice and guidance on spotting and dealing with phishing emails for consumers – it also operates a phishing reporting service that as of April 2025 has received over 41 million scam reports – bodies like HMRC cannot rely on everybody having visited the NCSC’s website. As such, Mike Britton, chief information officer (CIO) at Abnormal AI, a specialist in phishing, social engineering and account takeover prevention, argued that HMRC could and should have done more from a technical perspective. “Governments will always be a high tier target for cyber criminals due to the valuable information they hold. In fact, attacks against this sector are rising,” he said. “In this case, it looks like criminals utilised account take over to conduct fraud. To combat this, multifactor authentication (MFA) is key, but as attacks grow more sophisticated, further steps must be taken.” Britton said organisations like HMRC really needed to consider adopting more layered security strategies, not only including MFA but also incorporating wider visibility and unified controls across its IT systems. Account takeover attacks such as the ones seen in this incident can unfold quickly, he added, so its cyber function should also be equipped with the tools to identify and remediate compromised accounts on the fly. Read more about trends in phishing Quishing, meaning QR code phishing, is an offputting term for an on-the-rise attack method. Learn how to defend against it. A healthy dose of judicious skepticism is crucial to preventing phishing attacks, said David Fine, supervisory special agent at the FBI, during a presentation at a HIMSS event. Exchange admins got a boost from Microsoft when it improved how it handles DMARC authentication failures to help organisations fight back from email-based attacks on their users.

Cybersecurity researchers have flagged several popular Google Chrome extensions that have been found to transmit data in HTTP and hard-code secrets in their code, exposing users to privacy and security risks. "Several widely used extensions [...] unintentionally transmit sensitive data over simple HTTP," Yuanjing Guo, a security researcher in the Symantec's Security Technology and Response team, said. "By doing so, they expose browsing domains, machine IDs, operating system details, usage analytics, and even uninstall information, in plaintext." The fact that the network traffic is unencrypted also means that they are susceptible to adversary-in-the-middle (AitM) attacks, allowing malicious actors on the same network such as a public Wi-Fi to intercept and, even worse, modify this data, which could lead to far more serious consequences. The list of identified extensions are below - SEMRush Rank (extension ID: idbhoeaiokcojcgappfigpifhpkjgmab) and PI Rank (ID: ccgdboldgdlngcgfdolahmiilojmfndl), which call the URL "rank.trellian[.]com" over plain HTTP Browsec VPN (ID: omghfjlpggmjjaagoclmmobgdodcjboh), which uses HTTP to call an uninstall URL at "browsec-uninstall.s3-website.eu-central-1.amazonaws[.]com" when a user attempts to uninstall the extension MSN New Tab (ID: lklfbkdigihjaaeamncibechhgalldgl) and MSN Homepage, Bing Search & News (ID: midiombanaceofjhodpdibeppmnamfcj), which transmit a unique machine identifier and other details over HTTP to "g.ceipmsn[.]com" DualSafe Password Manager & Digital Vault (ID: lgbjhdkjmpgjgcbcdlhkokkckpjmedgc), which constructs an HTTP-based URL request to "stats.itopupdate[.]com" along with information about the extension version, user's browser language, and usage "type" "Although credentials or passwords do not appear to be leaked, the fact that a password manager uses unencrypted requests for telemetry erodes trust in its overall security posture," Guo said. Symantec said it also identified another set of extensions with API keys, secrets, and tokens directly embedded in the JavaScript code, which an attacker could weaponize to craft malicious requests and carry out various malicious actions - Online Security & Privacy extension (ID: gomekmidlodglbbmalcneegieacbdmki), AVG Online Security (ID: nbmoafcmbajniiapeidgficgifbfmjfo), Speed Dial [FVD] - New Tab Page, 3D, Sync (ID: llaficoajjainaijghjlofdfmbjpebpa), and SellerSprite - Amazon Research Tool (ID: lnbmbgocenenhhhdojdielgnmeflbnfb), which expose a hard-coded Google Analytics 4 (GA4) API secret that an attacker could use to bombard the GA4 endpoint and corrupt metrics Equatio – Math Made Digital (ID: hjngolefdpdnooamgdldlkjgmdcmcjnc), which embeds a Microsoft Azure API key used for speech recognition that an attacker could use to inflate the developer's costs or exhaust their usage limits Awesome Screen Recorder & Screenshot (ID: nlipoenfbbikpbjkfpfillcgkoblgpmj) and Scrolling Screenshot Tool & Screen Capture (ID: mfpiaehgjbbfednooihadalhehabhcjo), which expose the developer's Amazon Web Services (AWS) access key used to upload screenshots to the developer's S3 bucket Microsoft Editor – Spelling & Grammar Checker (ID: gpaiobkfhnonedkhhfjpmhdalgeoebfa), which exposes a telemetry key named "StatsApiKey" to log user data for analytics Antidote Connector (ID: lmbopdiikkamfphhgcckcjhojnokgfeo), which incorporates a third-party library called InboxSDK that contains hard-coded credentials, including API keys. Watch2Gether (ID: cimpffimgeipdhnhjohpbehjkcdpjolg), which exposes a Tenor GIF search API key Trust Wallet (ID: egjidjbpglichdcondbcbdnbeeppgdph), which exposes an API key associated with the Ramp Network, a Web3 platform that offers wallet developers a way to let users buy or sell crypto directly from the app TravelArrow – Your Virtual Travel Agent (ID: coplmfnphahpcknbchcehdikbdieognn), which exposes a geolocation API key when making queries to "ip-api[.]com" Attackers who end up finding these keys could weaponize them to drive up API costs, host illegal content, send spoofed telemetry data, and mimic cryptocurrency transaction orders, some of which could see the developer's ban getting banned. Adding to the concern, Antidote Connector is just one of over 90 extensions that use InboxSDK, meaning the other extensions are susceptible to the same problem. The names of the other extensions were not disclosed by Symantec. "From GA4 analytics secrets to Azure speech keys, and from AWS S3 credentials to Google-specific tokens, each of these snippets demonstrates how a few lines of code can jeopardize an entire service," Guo said. "The solution: never store sensitive credentials on the client side." Developers are recommended to switch to HTTPS whenever they send or receive data, store credentials securely in a backend server using a credentials management service, and regularly rotate secrets to further minimize risk. The findings show how even popular extensions with hundreds of thousands of installations can suffer from trivial misconfigurations and security blunders like hard-coded credentials, leaving users' data at risk. "Users of these extensions should consider removing them until the developers address the insecure [HTTP] calls," the company said. "The risk is not just theoretical; unencrypted traffic is simple to capture, and the data can be used for profiling, phishing, or other targeted attacks." "The overarching lesson is that a large install base or a well-known brand does not necessarily ensure best practices around encryption. Extensions should be scrutinized for the protocols they use and the data they share, to ensure users' information remains truly safe." Found this article interesting? Follow us on Twitter  and LinkedIn to read more exclusive content we post.

Billionaire Elon Musk has countered president Donald Trump's threat to "terminate Elon’s Governmental Subsidies and Contracts," in spectacular fashion: by threatening to cut off the United States' access to outer space."In light of the President’s statement about cancellation of my government contracts, SpaceX will begin decommissioning its Dragon spacecraft immediately," Musk tweeted.But it didn't take him long to blink. A few hours later — and after the publication of this story — Musk reversed course, agreeing to "cool off" and saying that "we won't decommission Dragon."That's not surprising. As executives at SpaceX no doubt desperately tried to explain to him after the dustup, the company would be in terrible danger without all the money it gets from NASA.And if Musk were to make good on his threat, the United States' space program could experience a setback of epic proportions. SpaceX's Dragon spacecraft has quickly become the de facto method for NASA astronauts to travel to the International Space Station.In other words, the threat could prevent American astronauts from visiting the space station — especially considering that the only other American option, Boeing's Starliner, is likely still years away from becoming a viable alternative, if ever.It was a significant escalation in a major falling out between the world's most powerful man and its richest one. The pair have been openly feuding about Trump's so-called "big, beautiful bill," culminating in threats and personal attacks.The collateral damage of the feud could be enormous, particularly for the US space program.Ars Technica's Eric Berger suggested that Trump ripping up Musk's government contracts "would both end the International Space Station and simultaneously provide no way to safely deorbit it.""This just gets better and better," Musk replied in a laughing emoji-laden tweet. "Go ahead, make my day…"The news comes after the Trump administration abruptly pulled its nominee for the NASA administrator role, Jared Isaacman.Isaacman, who was hand-picked by Musk, has been to space twice with the help of SpaceX.The news greatly angered Musk, causing him to go on a crusade against Trump's tax bill.Musk's latest threats to decommission SpaceX's Dragon spacecraft could put the Trump administration and NASA in an extremely unfortunate position. Apart from Boeing's much-maligned Starliner, which has yet to complete a successful crewed mission to the ISS, the only alternative to send astronauts to the space station is Russia's Soyuz spacecraft.While the station's days are already numbered — NASA recently awarded SpaceX a contract to decommission the orbital lab in 2030 — continuing operations could prove extremely difficult without Dragon.But whether Musk will make good on his threat remains to be seen, especially considering the billionaire has a lengthy track record of making empty promises.Apart from vowing to decommission Dragon, Musk also attempted to smear Trump's name by arguing that he's "in the Epstein files.""This is the real reason they have not been made public," he tweeted. "Have a nice day, DJT!"Musk is clearly out for blood, even officially calling for Trump to be impeached and replaced by his vice president JD Vance.Who will emerge victorious is anybody's guess. If there's one certainty, it won't be NASA. The agency is expected to be hit by brutal cuts that could lay waste to dozens of space missions.Share This Article

Remember that time when good ol’ Peter Parker called a drone strike on his classmates because another guy was flirting with MJ? Well, the artificial intelligence that made it happen is back, this time in snarky Canadian form! Deadline is reporting that Schitt’s Creek alum Emily Hampshire has been cast as E.D.I.T.H. in Vision Quest, the upcoming Disney+ series starring Paul Bettany as the synthezoid Avenger. E.D.I.T.H., of course, made her debut as a pair of ugly, gaudy sunglasses the late Tony Stark bequeathed to Peter in Spider-Man: Far From Home. Through E.D.I.T.H., Peter had access to vast technological resources, resources that Mysterio wanted to use for himself. At the end of Far From Home, Peter reclaimed the E.D.I.T.H. glasses and in Spider-Man: No Way Home, a screen readout assured us that they were inactive. Moreover, No Way Home ends with Peter having his secret identity wiped from everyone’s memory and a closing shot of him hand-stitching his own costume in a dingy New York apartment, suggeting that the MCU experiment of making working-class Peter Parker into the scion of a tech bro was done. That may still be true, in which case Vision Quest is a much better place for E.D.I.T.H. to exist. Created by Terry Matalas, showrunner of the Twelve Monkeys TV series and the third season of Star Trek: Picard, Vision Quest will follow the next phase in the life of the synthezoid Vision, who was killed in Avengers: Infinity War and resurrected as an initially evil clone in WandaVision. The title Vision Quest comes from a 1989-1990 arc of West Coast Avengers, written and penciled by John Byrne, in which the U.S. government dismantles Vision and recreates him into a mindless and easily controllable form, signified by his new bleach white look. Fans of the MCU will recognize that storyline from the last episodes of WandaVision, in which S.A.B.E.R. did the same thing to Bettany’s character. However, the Vision Quest comics continued to tell the story of Vision attempting to recover the humanity and personality he’d previously gained over the years, which will presumably be the plot of Vision Quest. However, E.D.I.T.H.’s casting is just the latest in a host of synthetic characters who will appear in the show. James Spader will return as Vision’s creator Ultron, and T’Nia Miller has joined the show as Jocasta, a female synthezoid originally created as Ultron’s bride. A few humans will show up as well, including the return of Faran Tahir as Raza, the leader of the Ten Rings terrorist cell, last seen in Iron Man, and frequent Matalas collaborator Todd Stashwick as a mystery man hunting Vision. That’s a packed cast, but as anyone who recalls the Picard season 3 episode in which androids Data and Lore merged, Matalas knows how to tell an interesting story about artificial intelligence. That episode also showed that Matalas knows how to add levity to heavy conversations about existence, making Hampshire’s casting as E.D.I.T.H. a wise choice. Just don’t let her anywhere near another school bus full of teenagers. Vision Quest is slated to appear on Disney+ in 2026.

When it comes to Apple, all eyes are on AI. Generative AI (genAI) is the most disruptive technology we’ve seen in years; it is weaving itself into all parts of life – so why should IT management be left unscathed? It won’t be, and the latest AI-powered IT management features within the Jamf platform will soon be the kind of tools IT expects. Jamf is a leading Apple-in-the-enterprise device management (and security vendor recently began offering enterprise support for Android devices). The company has been working away on AI features to support its solutions for some time, and has at last introduced some of these at its Jamf Nation Live event. The tools are designed to boost efficiency and support better decision-making when it comes to handling your fleets. Of course, you’d expect anyone fielding genAI solutions to say something like that, so what do these tools do? Introducing Jamf AI Assistant Available as a beta, AI Assistant is designed to support tech support! That means it will help IT admins find what they need and help them understand how and why devices they do find are configured. Jamf splits these two paths into two categories: Search skill and Explain skill. Search skill lets admins perform natural language inventory queries across their managed fleets, enabling them to quickly find devices within their flotilla that meet the search parameters. The goal is to make it quicker and easier to audit managed devices for compliance, and to troubleshoot when things go wrong. Explain skill caters to another facet of an IT admin’s daily challenges. As Jamf explains, it means the genAI can translate complex configurations and policies into clear, easy-to-understand language. This helps admins make informed decisions, streamline troubleshooting and manage policies more confidently, says Jamf. While these new Jamf tools don’t automate much of the workload facing IT, it’s not hard to see how once the AI can understand what’s happening on a Mac and identify those devices that meet a set of parameters, the only missing piece is to automate some of the workflow in between. This, of course, is the direction of travel and will likely ripple across IT and every platform. Who knows, it might even make the cost of supporting Windows fleets almost as affordable as that of managing fleets of Apple devices. (Though I doubt it.) Beyond AI Jamf also made a handful of announcements outside of AI, including the general availability of Blueprints, a set of tools the company announced at JNUC last year. Blueprints builds on Apple’s Declarative Device Management framework and is designed to simplify and accelerate device configuration by consolidating policies, profiles and restrictions into a single, unified workflow. This makes a lot of sense on a road map to further AI deployment, as well as for anyone attempting to manage and deploy large Apple fleets. I imagine admins preparing for mammoth college- or school-wide deployments will have some optimism that Blueprints could help save time. Don’t neglect that education tech is expected to deploy thousands of devices in a few weeks, so these tools should be significant to them. Jamf continues working on Blueprints, and has introduced a beta release of Configuration Profiles within Blueprints. This tech consists of a new dynamic framework designed to help teams manage devices at scale, thanks to the new dynamic framework for MDM key delivery. Ticket to ride Jamf has offered a Self Service+ portal since earlier this year. Aimed at end-users, the system lets users request, download and update apps, as well as monitor their device security. Those features have been expanded with identity management tools, so users can view their accounts change passwords, and request things like temporary admin access. The beauty of Self Service+ is that it enables users to do these things autonomously while keeping their devices fully auditable and compliant. The idea is that it’s a lot better to focus the expensive tech support teams on the big problems, rather than seeing them bogged down in small, transient (albeit important), challenges.  The company also introduced Compliance Benchmarks. Based on Apple’s macOS Security Compliance Project (mSCP), this system helps IT automate the process of securing their Apple devices. Jamf has also added malware detection to its App Installers module, which means every application made available through that system is scanned to maintain security confidence. That’s really important to companies attempting to provision apps to employees, particularly if they want to avoid accidental installs of hacked malware posing as the original app. You can follow me on social media! Join me on BlueSky,  LinkedIn, and Mastodon.