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.

The murder of John Forde was the culmination to years of political, social, and criminal intrigue.   Get the Popular Science daily newsletter💡 Breakthroughs, discoveries, and DIY tips sent every weekday. Researchers have uncovered handwritten letters, court documents, and a coroner’s report related to the nearly 700-year-old cold case murder of a medieval priest. Published on June 5 in the journal Criminal Law Forum, the investigation draws on direct archival evidence from Cambridge University that is helping fill in the gaps to a high-profile true crime scandal that would make headlines even today. But despite a mountain of firsthand accounts, the murder’s masterminds never saw justice. The ‘planned and cold-blooded’ crime On Friday, May 3, 1337, Anglican priest John Forde began a walk along downtown London’s Cheapside street after vespers (evening prayers) shortly before sunset. At one point, a clergyman familiar to Forde by the name of Hasculph Neville approached him to begin a “pleasant conversation.” As the pair neared St. Paul’s Cathedral, four men ambushed the priest. One of the attackers then proceeded to slit Forde’s throat using a 12-inch dagger as two other assailants stabbed him in the stomach in front of onlookers. The vicious crime wasn’t a brazen robbery or politically motivated attack. It was likely a premeditated murder orchestrated by Ela Fitzpayne, a noblewoman, London crime syndicate leader—and potentially Forde’s lover. “We are looking at a murder commissioned by a leading figure of the English aristocracy. It is planned and cold-blooded, with a family member and close associates carrying it out, all of which suggests a revenge motive,” Cambridge University criminology professor Manuel Eisner explained in a statement. The location of the murder of John Forde on May 3, 1337. Credit: Medieval Murder Maps / University of Cambridge’s Institute of Criminology / Historic Towns Trust. A longstanding feud To understand how such a brutal killing could take place in daylight on a busy London street, it’s necessary to backtrack at least five years. In January 1332, the Archbishop of Canterbury sent a letter to the Bishop of Winchester that included a number of reputation-ruining claims surrounding Fitzpayne. In particular, Archbishop Simon Mepham described sexual relationships involving “knights and others, single and married, and even with clerics in holy orders.” The wide-ranging punishments for such sinful behavior could include a prohibition on wearing gold and other precious jewelry, as well as large tithes to monastic orders and the poor. But the most humiliating atonement often came in the form of a public walk of shame. The act of contrition involved walking barefoot across Salisbury Cathedral—England’s longest nave—in order to deliver a handcarried, four-pound wax candle to the church altar. What’s more, Archbishop Mepham commanded that Fitzpayne must repeat this penance every autumn for seven years. Fitzpayne was having none of it. According to Mepham’s message, the noblewoman chose to continue listening to a “spirit of pride” (and the devil), and refused to abide by the judgment. A second letter sent by the Archbishop that April also alleged that she had since absconded from her husband, Sir Robert Fitzpayne, and was hiding in London’s Rotherhithe district along the Thames River. Due to this, Archbishop Mepham reported that Ela Fitzpayne had been excommunicated from the church. Image of the Archbishop of Canterbury’s letters to the Bishop of Winchester on the subject of Ela Fitzpayne, from the register of John de Stratford. Credit: Hampshire Archives and Hampshire County Council. Raids and rats But who tipped the clergy off to her indiscretions? According to Eisner’s review of original documents as part of the Cambridge University Institute of Criminology’s Medieval Murder Maps project, it was almost certainly her ex-lover, the soon-to-be-murdered John Forde. He was the only alleged lover named in Archbishop Mepham’s letters, and served as a church rector in a village located on the Fitzpayne family’s estate at the time of the suspected affair.  “The archbishop imposed heavy, shameful public penance on Ela, which she seems not to have complied with, but may have sparked a thirst for vengeance,” Eisner said. “Not least as John Forde appears to have escaped punishment by the church.” But Forde’s relationship with the Fitzpaynes seems to have extended even more illicit activities. In another record reviewed by Eisner, both Ela Fitzpayne and John Forde had been indicted by a Royal Commission in 1322. The crime–assisting in the raid of a Benedictine priory alongside Sir Fitzpayne. They and others reportedly assaulted the priory a year earlier, making off with around 18 oxen, 30 pigs, and 200 sheep. The monastery coincidentally served as a French abbey’s outpost amid increasing tensions between France and England in the years leading up to the Hundred Years’ War. Archbishop Mepham was almost certainly displeased after hearing about the indictment of one of his own clergy. A strict administrator himself, Mepham “was keen to enforce moral discipline among the gentry and nobility,” added Eisner. He theorizes that Forde copped to the affair after getting leaned on by superiors, which subsequently led to the campaign to shame Ela Fitzpayne as a means to reassert the Church’s authority over English nobility. Forde, unfortunately, was caught between the two sides. “John Forde may have had split loyalties,” argued Eisner. “One to the Fitzpayne family, who were likely patrons of his church and granted him the position. And the other to the bishops who had authority over him as a clergy member.” Archbishop Mepham ultimately wouldn’t live to see the scandal’s full consequences. Fitzpayne never accepted her walk of shame, and the church elder died a year after sending the incriminating letters. Eisner believes the Fitzpaynes greenlit their hit job on Forde only after the dust had seemingly settled. It doesn’t help their case three bystanders said the man who slit the rector’s throat was none other than Ela Fitzpayne’s own brother, Hugh Lovell. They also named two family servants as Forde’s other assailants. Archbishop Mepham died four years before Forde’s murder. Credit: ampshire Archives and Hampshire County Council Turning a blind eye Anyone waiting for justice in this medieval saga will likely be disappointed. “Despite naming the killers and clear knowledge of the instigator, when it comes to pursuing the perpetrators, the jury turn[ed] a blind eye,” Eisner said. Eisner explained the circumstances surrounding an initial lack of convictions were simply “implausible.” No one supposedly could locate the accused to bring to trial, despite the men belonging to one of England’s highest nobility houses. Meanwhile, the court claimed Hugh Lovell had no belongings available to confiscate. “This was typical of the class-based justice of the day,” said Eisner. In the end, the only charge that ever stuck in the murder case was an indictment against one of the family’s former servants. Five years after the first trial in 1342, Hugh Colne was convicted of being one of the men to stab Forde in the stomach and sentenced to the notorious Newgate Prison. As dark and sordid as the multiyear medieval drama was, it apparently didn’t change much between Ela Fitzpayne and her husband, Sir Robert. She and the baron remained married until his death in 1354—when she subsequently inherited all his property. “Where rule of law is weak, we see killings committed by the highest ranks in society, who will take power into their own hands, whether it’s today or seven centuries ago,” said Eisner. That said, the criminology professor couldn’t help but concede that Ela Fitzpayne was an “extraordinary” individual, regardless of the era. “A woman in 14th century England who raided priories, openly defied the Archbishop of Canterbury, and planned the assassination of a priest,” he said. “Ela Fitzpayne appears to have been many things.”

Published June 5, 2025 10:00am EDT close Don’t be so quick to click that Google calendar invite. It could be a hacker’s trap Cybercriminals are sending fake meeting invitations that seem legitimate. NEWYou can now listen to Fox News articles! Americans’ personal data is now spread across more digital platforms than ever. From online shopping habits to fitness tracking logs, personal information ends up in hundreds of company databases. While most people worry about social media leaks or email hacks, a far less visible threat comes from data brokers.I still find it hard to believe that companies like this are allowed to operate with so little legal scrutiny. These firms trade in personal information without our knowledge or consent. What baffles me even more is that they aren’t serious about protecting the one thing that is central to their business model: data. Just last year, we saw news of a massive data breach at a data broker called National Public Data, which exposed 2.7 billion records. And now another data broker, LexisNexis, a major name in the industry, has reported a significant breach that exposed sensitive information from more than 364,000 people. A hacker at work (Kurt "CyberGuy" Knutsson)LexisNexis breach went undetected for months after holiday hackLexisNexis filed a notice with the Maine attorney general revealing that a hacker accessed consumer data through a third-party software development platform. The breach happened on Dec. 25, 2024, but the company only discovered it months later. LexisNexis was alerted on April 1, 2025, by an unnamed individual who claimed to have found sensitive files. It remains unclear whether this person was responsible for the breach or merely came across the exposed data.MASSIVE DATA BREACH EXPOSES 184 MILLION PASSWORDS AND LOGINSA spokesperson for LexisNexis confirmed that the hacker gained access to the company’s GitHub account. This is a platform commonly used by developers to store and collaborate on code. Security guidelines repeatedly warn against storing sensitive information in such repositories; however, mistakes such as exposed access tokens and personal data files continue to occur.The stolen data varies from person to person but includes full names, birthdates, phone numbers, mailing and email addresses, Social Security numbers and driver's license numbers. LexisNexis has not confirmed whether it received any ransom demand or had further contact with the attacker. An individual working on their laptop (Kurt "CyberGuy" Knutsson)Why the LexisNexis hack is a bigger threat than you realizeLexisNexis isn’t a household name for most people, but it plays a major role in how personal data is harvested and used behind the scenes. The company pulls information from a wide range of sources, compiling detailed profiles that help other businesses assess risk and detect fraud. Its clients include banks, insurance companies and government agencies.In 2023, the New York Times reported that several car manufacturers had been sharing driving data with LexisNexis without notifying vehicle owners. That information was then sold to insurance companies, which used it to adjust premiums based on individual driving behavior. The story made one thing clear. LexisNexis has access to a staggering amount of personal detail, even from people who have never willingly engaged with the company.Law enforcement also uses LexisNexis tools to dig up information on suspects. These systems offer access to phone records, home addresses and other historical data. While such tools might assist in investigations, they also highlight a serious issue. When this much sensitive information is concentrated in one place, it becomes a single point of failure. And as the recent breach shows, that failure is no longer hypothetical. A hacker at work (Kurt "CyberGuy" Knutsson)7 expert tips to protect your personal data after a data broker breachKeeping your personal data safe online can feel overwhelming, but a few practical steps can make a big difference in protecting your privacy and reducing your digital footprint. Here are 7 effective ways to take control of your information and keep it out of the wrong hands:1. Remove your data from the internet: The most effective way to take control of your data and avoid data brokers from selling it is to opt for data removal services. While no service promises to remove all your data from the internet, having a removal service is great if you want to constantly monitor and automate the process of removing your information from hundreds of sites continuously over a longer period of time. Check out my top picks for data removal services here.Get a free scan to find out if your personal information is already out on the web.2. Review privacy settings: Take a few minutes to explore the privacy and security settings on the services you use. For example, limit who can see your social media posts, disable unnecessary location-sharing on your phone and consider turning off ad personalization on accounts like Google and Facebook. Most browsers let you block third-party cookies or clear tracking data. The FTC suggests comparing the privacy notices of different sites and apps and choosing ones that let you opt out of sharing when possible.3. Use privacy-friendly tools: Install browser extensions or plugins that block ads and trackers (such as uBlock Origin or Privacy Badger). You might switch to a more private search engine (like DuckDuckGo or Brave) that doesn’t log your queries. Consider using a browser’s "incognito" or private mode when you don’t want your history saved, and regularly clear your cookies and cache. Even small habits, like logging out of accounts when not in use or using a password manager, make you less trackable.GET FOX BUSINESS ON THE GO BY CLICKING HERE4. Beware of phishing links and use strong antivirus software: Scammers may try to get access to your financial details and other important data using phishing links. The best way to safeguard yourself from malicious links is to have antivirus software installed on all your devices. This protection can also alert you to phishing emails and ransomware scams, keeping your personal information and digital assets safe. Get my picks for the best 2025 antivirus protection winners for your Windows, Mac, Android and iOS devices.5. Be cautious with personal data: Think twice before sharing extra details. Don’t fill out online surveys or quizzes that ask for personal or financial information unless you trust the source. Create separate email addresses for sign-ups (so marketing emails don’t go to your main inbox). Only download apps from official stores and check app permissions.6. Opt out of data broker lists: Many data brokers offer ways to opt out or delete your information, though it can be a tedious process. For example, there are sites like Privacy Rights Clearinghouse or the Whitepages opt-out page that list popular brokers and their opt-out procedures. The FTC’s consumer guide, "Your Guide to Protecting Your Privacy Online," includes tips on opting out of targeted ads and removing yourself from people-search databases. Keep in mind you may have to repeat this every few months.7. Be wary of mailbox communications: Bad actors may also try to scam you through snail mail. The data leak gives them access to your address. They may impersonate people or brands you know and use themes that require urgent attention, such as missed deliveries, account suspensions and security alerts.Kurt’s key takeawayFor many, the LexisNexis breach may be the first time they realize just how much of their data is in circulation. Unlike a social media platform or a bank, there is no clear customer relationship with a data broker, and that makes it harder to demand transparency. This incident should prompt serious discussion around what kind of oversight is necessary in industries that operate in the shadows. A more informed public and stronger regulation may be the only things standing between personal data and permanent exposure.CLICK HERE TO GET THE FOX NEWS APPShould companies be allowed to sell your personal information without your consent? Let us know by writing us atCyberguy.com/Contact.For more of my tech tips and security alerts, subscribe to my free CyberGuy Report Newsletter by heading to Cyberguy.com/Newsletter.Ask Kurt a question or let us know what stories you'd like us to cover.Follow Kurt on his social channels:Answers to the most-asked CyberGuy questions:New from Kurt:Copyright 2025 CyberGuy.com. All rights reserved. Kurt "CyberGuy" Knutsson is an award-winning tech journalist who has a deep love of technology, gear and gadgets that make life better with his contributions for Fox News & FOX Business beginning mornings on "FOX & Friends." Got a tech question? Get Kurt’s free CyberGuy Newsletter, share your voice, a story idea or comment at CyberGuy.com.

Why building trust matters more than building components.There’s a scene in Field of Dreams that regularly comes to mind. Ray Kinsella (Kevin Costner) is standing at the edge of his cornfield ballpark, full of doubt about his ball field project. And then Terrence Mann (James Earl Jones) delivers this quiet but powerful monologue…James Earl Jones as Terrence Mann gives an inspiring speech“People will come, Ray. They’ll come to Iowa for reasons they can’t even fathom… They’ll arrive at your door as innocent as children, longing for the past… They’ll pass over the money without even thinking about it — for it is money they have and peace they lack.”It’s powerful. And there’s temptation for designers to think this way. That, if we just build it properly, people will come and use it. It’ll be a raving success. But that kind of thinking rests on emotion and hope. “People will come, Ray.”That got me thinking about my work with design systems. Because early on, that’s exactly how I imagined it would work.No…they won’t just come.I thought if you just built a great design system, people would come running from all over to use it. Designers would geek out. Engineers would contribute. PMs would rally around the time savings and consistency. I thought the system would basically sell itself. Job done.Except not. Not at first. In fact, most of those people actively resisted it. And it left me frustrated trying to figure out what was going on.That’s when it hit me: people don’t come just because you built something. They come because you built something that includes them. This isn’t a fictional baseball field built on faith. They don’t come because they don’t know it. It’s foreign. And as humans, we tend to run away from what we don’t understand.That’s why the people who work on design systems are so important. So that you can be known and your systems can be known. So that a relationship can be established. Trust can be created and people can see that this system will work for them. In fact, it’s been purpose-built for them.Design Systems are political (it’s true)I never would have imagined how political design systems would be. They seem logical and straightforward. It’s everything you need to build interfaces and consistent experiences. So, I thought the quality of the work would speak for itself. But once your system meets the real world, things get complicated. Real fast.Everyone already has established working patterns and people aren’t usually inclined to change. Plus, designers have their opinions. Engineers have priorities. Product managers have launch dates. And everyone already has a “good-enough solution”. So, now your carefully crafted design system feels more like a threat or liability than the life-changing birthday present you thought it’d be.You thought you were offering something amazing. They hear restriction. They see more steps. And they’re annoyed — at you — for meddling in their perfectly stable world.Why? Well, people love their tools. And, I mean LOVE them. They deeply cherish them. I think of the carpenter who’s used the same, trusty 20oz wood-handled hammer for 40 years. It’s weathered difficult projects and has dents and stains from 1,000s of projects. How do you convince someone to leave that hammer behind and pick up a new, unproven hammer for their work? It usually happens in community…in relationships.So, it turns out, building the system was the easy part. Getting people to care about it? That’s the real work. And that’s where building relationships comes in.The real work: building relationshipsTrue adoption doesn’t happen through documentation or a flashy campaign.So you can’t rely on a “build it and they will come” mentality. It means you need to make time to understand the people you’re building for and with. Because if it isn’t theirs, it won’t matter how good it is. Every group has different motivations, pain points, and goals. If you want them on board, you have to speak to them, about them, and how your system will help them.Designers need to see how the system supports creativity, not stifles it. Demonstrate how it will help them be more effective in their work.Engineers care about stability, performance, and clean code. Show them the efficiency that it brings to their development pipelines.PMs are focused on delivery. Make the system reduce friction and risk.Executives want the business case to be clear. Show them how your system enables faster velocity, better consistency, and reduced maintenance cost.Establishing how individual goals come together as shared goals is critical.Sounds selfish, right? Not really. They’re paid to do their job, and if you want your design system to be successful, it has to make them successful. So if you can’t answer a need to any of your partners or stakeholders, go back and figure out how to create that kind of value…or start with the people where the value already is.It’s the relationships that shift the dynamic. Suddenly it’s not “my design system vs. their priorities”…it’s shared ownership…our collective win.You can’t enforce your way to powerful adoptionYour first instinct might be to skip the relationships and rely on the “because I said so” method. So you add mandates. Governance councils. Approval gates. But none of them really work. You’ll have people subvert the system, or hold so fearfully tight to it that it hurts the product experience in the end.People don’t adopt systems because they have to. They adopt them because they believe in them. And belief is earned, not enforced. Your job is to find the intrinsic motivation that will cause them to jump on board and be a raving fan spreading the good news of your system. And that can’t be a marketing slogan or tagline; it has to be built into the design system.The goal isn’t to control usage…it’s to cultivate trust, leading to usage. It’s better to have ten enthusiastic partners than a hundred reluctant rule-followers. Because those ten partners? They’ll advocate for you. They’ll give real feedback. They’ll make the system better.It sounds uncomfortable, but it’s best to trade policing behavior for building partnerships. That’s the moment your system will truly grow. Because trust is a currency that earns interest.Trust is the real foundationDesign systems rely on a strong foundation: principles, guidelines, tokens, styles, components, and more. But that foundation must be built on something critical: trust.Trust is what makes someone choose the system instead of rolling their own. It’s what keeps your system on their radar when everything’s on fire. It’s what makes people reach out to work it out together, instead of working around you and subverting the whole thing.Without trust, your system is just a nice idea. It’s relegated to pixel art. But with relationships that foster trust…they see how the system becomes indispensable. It’s their go-to secret weapon for success.Trust and relationships are the ground that all foundations are built on.I’ve been on both sides. I’ve had teams avoid the system because they didn’t trust it…because they didn’t trust me. Here’s the secret: I know them or how to serve them…no trust. On the flip side, I’ve seen teams move faster, smoother, and more confidently because we’d built a foundation of partnership over time.Trust isn’t a side effect. It’s not a nice-to-have. It’s the ground that holds the whole thing up. Without it, your design system is drifting in the outer cosmos. Relationships are the gravity that keeps your design system grounded in trust.They’ll come… but only if you earn itSo, I hate to break it to you, but the truth is…no one’s coming just because your system is well-made. There’s already a plethora of well-made systems out there ready to leave you disappointed.They’re busy with the newest top priority. They’ve been burned by “that type of system” before. They see you as a risk, not a partner. But…if you spend time knowing them… if you listen… if you build trust… if you make it feel like it’s theirs… well then… “…they will come…”They’ll message you before they start a new feature. They’ll advocate for tokens during sprint planning. They’ll tell others it saved them time. They’ll ask how they can help improve it.They won’t come for the components. They’ll come for what the system gives them: clarity. Consistency. Relief.And if you’ve done the hard, human work behind the system? Well then, you might just look up one day and realize that there’s a whole bunch of people in your Iowa ball field.The politics of Design Systems was originally published in UX Collective on Medium, where people are continuing the conversation by highlighting and responding to this story.

Two members of a group of cybercriminals named ViLE were sentenced this week for hacking into a federal law enforcement web portal in an extortion scheme. [...]

There’s a problem with today’s AI development tools. Vibe coding platforms are impressive and fun, but net-new code is useless when you already have a production codebase. Meanwhile, AI IDEs are powerful and interface with existing code, but they’re complex and developer-only.Builder fills this gap. It's not another AI coding toy—it's an enterprise-grade development platform and visual canvas that plugs into your existing React and Material UI projects. It understands your code, respects your design decisions, and your whole team can use it, not just devs.Builder: The AI-powered visual canvasBuilder is Git-backed, AI-powered, visually responsive, and capable of Figma-like design edits.Connect existing React and Material UI reposConnect any GitHub repo, including monorepo and multi-repo setups. Builder works from fresh branches (never Main), offers preview URLs, and creates AI-generated PRs.Once your project loads, try writing a prompt like, "make the hero image full-width,” or "add a Users dashboard at the /users route.”Use Material UI and your custom componentsBuilder adheres to your specific design systems and component libraries. Need all your code pinned to MUI v5.1? Should every new button use your team's custom <Button/>? Builder intelligently finds and matches your design system patterns.Wire up all your APIsConnecting APIs is easy with Builder. Its no-code nature empowers the non-developers on your team to build sophisticated solutions, too. Try a prompt like, “Fetch customer data from Supabase and render it as MUI grid."Edit React components visually with pixel-perfect precisionYou can't create truly pixel-perfect UIs with AI prompts alone. Need to subtly adjust a Card's elevation or push a Container five pixels to the left on mobile? Use Builder's visual controls, and it will update the code with the correct MUI props. It’s like an AI-first Figma replacement.Leverage our rich Figma to React integrationBuilder speaks fluent Figma. It can turn individual frames into components, merge multiple frames into complex layouts, or reference designs against existing elements. Builder also maps Figma components to their equivalent Material UI components, saving your devs hours of toil.Drag and drop anything for extra contextDrop in files for extra context—documents, PDFs, and screenshots all work. You can also use the @ keyword to reference other files in your codebase. The AI will analyze your reference materials and suggest appropriate patterns.Push code changes to Github using our agentic PR workflowBuilder both generates code and ships it back to your codebase. It makes intelligent PRs straight to GitHub. Even better, you can then tag @builderio-bot in your comments, and then the agent will handle feedback, make updates, and even fix build issues.Built for whole team collaborationBuilder works for everyone and solves problems across your entire organization:Designers can ensure design consistency, validate responsiveness, and eliminate the endless "that's not quite right" feedback cycles. Developers can connect existing repos to a powerful AI agent and visual assistant, turbocharging their cycles and creating high-quality UIs without design support. Product managers can create quick iterations, A/B test different layouts, and keep momentum on product improvements. Design system teams can enforce consistency across large teams, onboard new developers, and ensure design system adoption succeeds at scale.Getting Started with Builder and React + MUI appsThere are two ways to start developing React and Material UI apps with Builder. First, navigate to the sidebar menu inside your Builder account. Then choose the Projects menu (the icon looks like GitHub’s Octocat). Then you can either:Connect your existing repositoryConnect your GitHub repo to Builder and start editing visually right away. Give it a prompt, like "Create a new admin dashboard. Use our styling patterns and existing components..." Now, try tweaking the output in the visual canvas or pushing an AI-generated PR back to GitHub.Start fresh with an ideaDon't have a project yet? No worries. Write a prompt like "Create a contact form with validation using react-hook-form and MUI best practices." Builder will generate everything from scratch using your specified framework, component library, and unique design languageTry Builder with your next project.

The cloud has changed everything. It’s faster, cheaper, and easier to scale than traditional infrastructure. Initially, most companies chose a single cloud provider. That’s no longer enough. Now, nearly 86% of businesses use more than one cloud. This approach—called multi-cloud—lets teams choose the best features from each provider. But it also opens the door to new security risks. When apps, data, and tools are scattered across platforms, managing security gets harder. And in today's world of constant cyber threats, ignoring cloud security is not an option. Let’s walk through real-world challenges and the best ways to protect business data in a multi-cloud environment. 1. Know What You’re Working With Start with visibility. Make a full inventory of the cloud platforms, apps, and storage your business uses. Ask every department—marketing, finance, HR—what tools they’ve signed up for. Many use services without informing IT. This is shadow IT, and it’s risky. Once you have the list, figure out what data lives where. Some workloads are low-risk. Others involve customer records, credit card data, or legal files. Prioritize those. 2. Build a Unified Security Strategy One of the biggest mistakes companies make is treating each cloud provider as a separate system. Every provider has its own rules, tools, and settings. If your security strategy is broken up, gaps will appear. Instead, aim for a single, connected approach. Use the same access rules, encryption standards, and monitoring tools across all clouds. You don’t want different policies on AWS and Azure—it just invites trouble. Tools like centralized dashboards, SIEM (Security Information and Event Management), and SOAR (Security Orchestration, Automation, and Response) help you keep everything in one place. 3. Enforce Strict Access Controls In a multi-cloud world, identity and access control are one of the hardest things to get right. Every platform has its own login system. Without proper integration, mistakes happen. Someone might get more access than they need, or never lose access when they leave the company. Stick to these practices: Use role-based access control. Limit permissions to the bare minimum. Turn on multi-factor authentication. Link logins across platforms using identity federation. The more consistent your access rules are, the easier it is to control who gets in and what they can do. 4. Use the Zero Trust Model Zero Trust means never assume anything is safe. Every user, device, and app must prove itself—every time. Even if a user is on your network, don’t trust them by default. This model reduces risk. It checks each request. It verifies users. And it looks for signs of abnormal behavior, like someone logging in from a new device or country. Zero Trust works well with automation and real-time monitoring. It also forces teams to rethink how data is shared and accessed. 5. Encrypt Data—Always Encryption is a basic but powerful layer of defense. It protects data whether it’s sitting in storage or moving between systems. If attackers get in, encrypted data is useless without the keys. Most cloud platforms offer built-in encryption. But don’t rely only on that. You can manage your own keys with tools like AWS KMS or Azure Key Vault. That gives you more control. To stay safe: Encrypt both at rest and in transit. Avoid default settings. Rotate encryption keys regularly. 6. Monitor in Real Time Security is not a one-time task. You need to watch your systems around the clock. Set alerts for things like large file downloads, unusual logins, or traffic spikes. Centralized monitoring helps a lot. It pulls logs from all your platforms and tools into one place. That way, your security team isn’t flipping between dashboards when something goes wrong. Also, use automation to filter out noise and surface real threats faster. 7. Set Up Regular Audits and Compliance Checks Multi-cloud setups are great for flexibility, but complex when it comes to compliance. Each platform has its own set of controls and certifications. Managing them all can be overwhelming. That’s why audits matter. Run security checks on a regular schedule—monthly, quarterly, or after every major change. Look for misconfigured permissions, missing patches, or unsecured data. And document everything. Also, make sure your tools help meet regulations like GDPR, HIPAA, or PCI DSS. Automated compliance scans can help stay on top of this. 8. Prevent Data Loss with Smart Policies Sensitive data is always at risk. Employees might share it by mistake. Attackers might try to steal it. That’s where Data Loss Prevention (DLP) comes in. DLP tools block unauthorized sharing of personal data, financial records, or internal files. You can create rules like “Don’t send customer SSNs over email” or “Block uploads of credit card data to personal drives.” DLP also supports compliance and helps avoid lawsuits or fines when accidents happen. 9. Automate Where You Can Manual work slows things down, and mistakes happen. That’s why automation is key in cloud security. Automate things like: Patch management Access reviews Backup schedules Security alerts Automation speeds up your response time. It also frees your security team to focus on serious issues, not routine tasks. 10. Centralized Security Control One major downside of multi-cloud isa lack of visibility. If you’re jumping between different tools for each cloud, you miss things. Instead, use a centralized security management system. It collects data from all clouds, shows risk levels, flags issues, and helps you fix them from one place. This unified view makes a huge difference. It helps you react faster and stay ahead of threats. Final Thought Cloud providers have made data storage and computing easier than ever. But with great power comes risk. Using multiple clouds gives more choice, but also more responsibility. Most businesses today are not ready. Only 15% have a mature multi-cloud security plan, says the 2023 Cisco Cyber Security Readiness Index. That means many are exposed. The good news? You can fix this. Start with simple steps. Know what you use. Lock it down. Watch it closely. Keep improving. And above all, treat cloud security not as a technical box to check, but as something critical to your business. Because in today’s world, a single breach can shut you down. And that’s too big a risk to ignore.

Menu Home News Hardware Gaming Mobile Finance Deals Reviews How To Wccftech Xiaomi Cannot Develop A Future In-House XRING Chipset Using TSMC’s 2nm Process Because Of The U.S. Crackdown On Specialized EDA Tools, Company Will Be Limited To The ‘N3E’ Node Omar Sohail • Jun 5, 2025 at 04:28am EDT The XRING 01 is a technological milestone, not just for Xiaomi, but it is also regarded as an achievement for China, and one that would make the U.S. government very nervous, because, like current-generation chipsets, the in-house solution has been mass produced on TSMC’s 3nm ‘N3E’ process. Unfortunately, Xiaomi’s progress might not scale past this threshold because the Trump administration has banned the export of EDA tools that are necessary to successfully fabricate a 2nm SoC. Tipster claims that EDA tools are mandatory in designing GAAFET structures, meaning that Xiaomi and its XRING division will be limited to TSMC’s ‘N3E’ node Since TSMC’s 2nm technology has a GAAFET structure, Weibo tipster Digital Chat Station states that it is imperative that Xiaomi gets hold of those EDA, or Electronic Design Automation tools. The Taiwanese semiconductor giant was reported to have begun accepting orders for 2nm wafers from April 1, with each unit estimated to cost $30,000. Among the regular trio of Apple, Qualcomm, and MediaTek, Xiaomi would count itself as one of TSMC’s customers. Sadly, with the recent development, the Chinese firm will be limited to the 3nm N3E node, facing a similar fate to Huawei. The latest claim also suggests that to possess the latest and greatest hardware in smartphone chipset technology, Xiaomi will have little choice but to continue relying on Qualcomm and MediaTek, which will unveil the Snapdragon 8 Elite Gen 2 and Dimensity 9500 later this year. Fortunately, restricting exports of cutting-edge machinery to China will only boost its resolve to continue the production of local EDA tools, but will this hardware be developed fast enough for the Xiaomi XRING 02 to be fabricated on TSMC’s 2nm process? We will have the answer to this question in the future. Readers should note that there is also the risk that the Trump administration enforces a massive ban on Xiaomi, preventing the latter from doing business with TSMC or Samsung in any way, shape, or form. While China is pursuing the manufacturing of custom EUV machinery to eliminate any overseas trade involvement, it may take several years for the country to achieve autonomy. News Source: Digital Chat Station Subscribe to get an everyday digest of the latest technology news in your inbox Follow us on Topics Sections Company Some posts on wccftech.com may contain affiliate links. We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to amazon.com © 2025 WCCF TECH INC. 700 - 401 West Georgia Street, Vancouver, BC, Canada

It’s easy to look at President Donald Trump’s second term and conclude that the less power and reach the federal government has, the better. After all, a smaller government might provide Trump or someone like him with fewer opportunities to disrupt people’s lives, leaving America less vulnerable to the whims of an aspiring autocrat. Weaker law-enforcement agencies could lack the capacity to enforce draconian policies. The president would have less say in how universities like Columbia conduct their business if they weren’t so dependent on federal funding. And he would have fewer resources to fundamentally change the American way of life.Trump’s presidency has the potential to reshape an age-old debate between the left and the right: Is it better to have a big government or a small one? The left, which has long advocated for bigger government as a solution to society’s problems, might be inclined to think that in the age of Trump, a strong government may be too risky. Say the United States had a single-payer universal health care system, for example. As my colleague Kelsey Piper pointed out, the government would have a lot of power to decide what sorts of medical treatments should and shouldn’t be covered, and certain forms of care that the right doesn’t support — like abortion or transgender health — would likely get cut when they’re in power. That’s certainly a valid concern. But the dangers Trump poses do not ultimately make the case for a small or weak government because the principal problem with the Trump presidency is not that he or the federal government has too much power. It’s that there’s not enough oversight.Reducing the power of the government wouldn’t necessarily protect us. In fact, “making government smaller” is one of the ways that Trump might be consolidating power.First things first: What is “big government”?When Americans are polled about how they feel about “big government” programs — policies like universal health care, Social Security, welfare for the poor — the majority of people tend to support them. Nearly two-thirds of Americans believe the government should be responsible for ensuring everyone has health coverage. But when you ask Americans whether they support “big government” in the abstract, a solid majority say they view it as a threat.That might sound like a story of contradictions. But it also makes sense because “big government” can have many different meanings. It can be a police state that surveils its citizens, an expansive regulatory state that establishes and enforces rules for the private sector, a social welfare state that directly provides a decent standard of living for everyone, or some combination of the three. In the United States, the debate over “big government” can also include arguments about federalism, or how much power the federal government should have over states. All these distinctions complicate the debate over the size of government: Because while someone might support a robust welfare system, they might simultaneously be opposed to being governed by a surveillance state or having the federal government involved in state and local affairs.As much as Americans like to fantasize about small government, the reality is that the wealthiest economies in the world have all been a product of big government, and the United States is no exception. That form of government includes providing a baseline social safety net, funding basic services, and regulating commerce. It also includes a government that has the capacity to enforce its rules and regulations.A robust state that caters to the needs of its people, that is able to respond quickly in times of crisis, is essential. Take the Covid-19 pandemic. The US government, under both the Trump and Biden administrations, was able to inject trillions of dollars into the economy to avert a sustained economic downturn. As a result, people were able to withstand the economic shocks, and poverty actually declined. Stripping the state of the basic powers it needs to improve the lives of its citizens will only make it less effective and erode people’s faith in it as a central institution, making people less likely to participate in the democratic process, comply with government policies, or even accept election outcomes.A constrained government does not mean a small governmentBut what happens when the people in power have no respect for democracy? The argument for a weaker and smaller government often suggests that a smaller government would be more constrained in the harm it can cause, while big government is more unrestrained. In this case, the argument is that if the US had a smaller government, then Trump could not effectively use the power of the state — by, say, deploying federal law enforcement agencies or withholding federal funds — to deport thousands of immigrants, bully universities, and assault fundamental rights like the freedom of speech. But advocating for bigger government does not mean you believe in handing the state unlimited power to do as it pleases. Ultimately, the most important way to constrain government has less to do with its size and scope and more to do with its checks and balances. In fact, one of the biggest checks on Trump’s power so far has been the structure of the US government, not its size. Trump’s most dangerous examples of overreach — his attempts to conduct mass deportations, eliminate birthright citizenship, and revoke student visas and green cards based on political views — have been an example of how proper oversight has the potential to limit government overreach. To be sure, Trump’s policies have already upended people’s lives, chilled speech, and undermined the principle of due process. But while Trump has pushed through some of his agenda, he hasn’t been able to deliver at the scale he promised. But that’s not because the federal government lacks the capacity to do those things. It’s because we have three equal branches of government, and the judicial branch, for all of its shortcomings in the Trump era, is still doing its most basic job to keep the executive branch in check. Reforms should include more oversight, not shrinking governmentThe biggest lesson from Trump’s first term was that America’s system of checks and balances — rules and regulations, norms, and the separate branches of government — wasn’t strong enough. As it turned out, a lot of potential oversight mechanisms did not have enough teeth to meaningfully restrain the president from abusing his power. Trump incited an assault on the US Capitol in an effort to overturn the 2020 election, and Congress ultimately failed in its duty to convict him for his actions. Twice, impeachment was shown to be a useless tool to keep a president in check.But again that’s a problem of oversight, not of the size and power of government. Still, oversight mechanisms need to be baked into big government programs to insulate them from petty politics or volatile changes from one administration to the next. Take the example of the hypothetical single-payer universal health care system. Laws dictating which treatments should be covered should be designed to ensure that changes to them aren’t dictated by the president alone, but through some degree of consensus that involves regulatory boards, Congress, and the courts. Ultimately, social programs should have mechanisms that allow for change so that laws don’t become outdated, as they do now. And while it’s impossible to guarantee that those changes will always be good, the current system of employer-sponsored health insurance is hardly a stable alternative.By contrast, shrinking government in the way that Republicans often talk about only makes people more vulnerable. Bigger governments — and more bureaucracy — can also insulate public institutions from the whims of an erratic president. For instance, Trump has tried to shutter the Consumer Financial Protection Bureau (CFPB), a regulatory agency that gets in the way of his and his allies’ business. This assault allows Trump to serve his own interests by pleasing his donors.In other words, Trump is currently trying to make government smaller — by shrinking or eliminating agencies that get in his way — to consolidate power. “Despite Donald Trump’s rhetoric about the size or inefficiency of government, what he has done is eradicate agencies that directly served people,” said Julie Margetta Morgan, president of the Century Foundation who served as an associate director at the CFPB. “He may use the language of ‘government inefficiency’ to accomplish his goals, but I think what we’re seeing is that the goals are in fact to open up more lanes for big businesses to run roughshod over the American people.” The problem for small-government advocates is that the alternative to big government is not just small government. It’s also big business because fewer services, rules, and regulations open up the door to privatization and monopolization. And while the government, however big, has to answer to the public, businesses are far less accountable. One example of how business can replace government programs is the Republicans’ effort to overhaul student loan programs in the latest reconciliation bill the House passed, which includes eliminating subsidized loans and limiting the amount of aid students receive. The idea is that if students can’t get enough federal loans to cover the cost of school, they’ll turn to private lenders instead. “It’s not only cutting Pell Grants and the affordability of student loan programs in order to fund tax cuts to the wealthy, but it’s also creating a gap where [private lenders] are all too happy to come in,” Margetta Morgan said. “This is the small government alternative: It’s cutting back on programs that provided direct services for people — that made their lives better and more affordable — and replacing it with companies that will use that gap as an opportunity for extraction and, in some cases, for predatory services.”Even with flawed oversight, a bigger and more powerful government is still preferable because it can address people’s most basic needs, whereas small government and the privatization of public services often lead to worse outcomes.So while small government might sound like a nice alternative when would-be tyrants rise to power, the alternative to big government would only be more corrosive to democracy, consolidating power in the hands of even fewer people (and businesses). And ultimately, there’s one big way for Trump to succeed at destroying democracy, and that’s not by expanding government but by eliminating the parts of government that get in his way.See More:

© Henrique Ferreira via Unsplash Finding property lines can be tricky, especially for individuals who are looking to purchase or list a home for sale. Conventional techniques, including engaging surveyors, are costly and labor-intensive. As an alternate solution, technology provides apps that profess to show property lines. This raises the question: How precise are these digital resources at demarcating boundary lines? The emergence of an app that shows property lines has revolutionized how property owners, buyers, and real estate professionals interact with land boundaries. These digital tools leverage advanced mapping technologies to provide visual representations of property boundaries, offering a more accessible alternative to traditional surveying methods while raising important questions about their accuracy and reliability. What Are Property Line Apps? Apps that display property lines use Geographic Information Systems (GIS) and satellite imagery. They offer users a visual display of land boundaries, most commonly available on smartphones or tablets. These apps are meant to help make property borders easier to identify and are a helpful tool for property owners, real estate agents, and buyers. These applications typically draw information from public records, county assessor data, and other official sources to create digital representations of property boundaries. Many also incorporate user-friendly features like measurement tools, parcel information displays, and the ability to save or share property data with others. How Various Factors Affect Accuracy Several factors impact the reliability of property line apps. First, the source of the data is significant. Apps usually have access to government databases and public records that vary in accuracy based on when the data was last refreshed. Second, GPS technology limitations impact accuracy. Although GPS technology is becoming more advanced, apps might still have discrepancies where tree cover or high buildings block signals from satellites and influence tracking accuracy. The resolution of satellite imagery also plays a crucial role in determining how precisely property lines can be displayed. Higher-resolution images allow for more detailed and accurate boundary placements, while lower-quality imagery may result in less precise representations. Additionally, the frequency of data updates affects whether the app reflects recent property divisions, consolidations, or boundary adjustments. Comparing Traditional Surveying and Apps Professional surveyors approach property line determination using high-precision equipment and established methodologies. This traditional approach yields highly accurate results with precise and legally enforceable boundaries. Apps offer more general information on property lines compared to professional surveys. While they are fast and convenient, they provide no substitute for the precision of a professional survey. App-generated boundaries should not be relied upon as definitive indications of legal property lines. Traditional surveys involve physical measurements taken directly on the property, considering historical markers, neighboring properties, and legal descriptions. In contrast, apps rely on digital interpretations of existing records, which may not account for all the nuances that a professional surveyor would observe in person. Advantages of property line applications App-Generated Property Lines Property line apps may have their limitations, but they do have valuable uses. They are useful for general assessments where an immediate overview of boundaries may be required. The applications also have user-friendly interfaces that allow a wider audience to use these applications and learn technical skills. Additionally, they are often enhanced with more functionalities, such as calculating areas and providing land parcel information, thus expanding their usefulness for users. According to the U.S. Bureau of Land Management, these digital tools have significantly increased public access to property information that was previously difficult to obtain without professional assistance. This democratization of property data allows property owners to be more informed about their land assets and helps potential buyers better understand properties of interest before making major decisions. Potential Limitations and Risks Property line apps may be convenient, but they have clear limitations. Since the data relies heavily on public records, data errors are common. It can be outdated or incomplete, which can lead to misunderstandings or disputes. In addition, these apps are incapable of recognizing legal nuances, such as easements or encroachments, which can significantly impact property rights and boundaries. There is also a risk that users might place too much confidence in app-generated boundaries when making important decisions. While these tools can provide helpful guidance, they should not be the sole basis for resolving boundary disputes, building structures near property lines, or making purchase decisions without professional verification. Best Practices for Users Users should follow a few best practices to make the best and most effective use of a property line app. Cross-referencing results with official records verifies data accuracy, minimizing potential inaccuracies. Moreover, when app data is paired with physical inspections, it provides a fuller picture of property lines. Advice from professionals, including surveyors or real estate agents, can also be beneficial, especially for legal transactions. For important matters such as property purchases, boundary disputes, or construction projects near property lines, it’s advisable to use apps as preliminary tools only, following up with professional surveys before making final decisions. Understanding the limitations of these digital tools helps users utilize them appropriately within a broader strategy for property boundary determination. Conclusion Instead, property line apps provide a convenient and accessible way to determine where your land ends and where your neighbor’s begins. Yet, the precision of these tools is contingent on multiple factors such as data sources and technological limitations. Although useful as an initial step, these tools should not be used, and they should not be used for legal purposes, instead of professional surveys. Users can properly contextualize property boundary information by understanding what these applications can and cannot do. Technology continues to shape how we deal with real estate by digitalizing and providing easy access to tools that simplify complex processes. These apps will likely improve accuracy over time and become increasingly integral to property transactions. Until then, users must balance convenience with reliability, ensuring that the information they obtain is helpful and accurate. Smart Technologytechnology by ArchEyes Team Leave a comment