Search this site

In early August 2026, a high-profile wave of voice phishing (vishing) attacks rattled Wall Street. Heavyweights like Citadel, Point72, Two Sigma, and Millennium Management found themselves in the crosshairs of a sophisticated, coordinated campaign. Attackers were not hunting for zero-day exploits or dropping malware into network perimeters. Instead, they simply picked up the phone. Using advanced AI voice cloning, threat actors impersonated trusted contacts, executives, and IT personnel. Their goal was straightforward: bypass traditional technical controls, exploit human trust, and trick employees into approving unauthorized fund transfers or handing over Multi-Factor Authentication (MFA) credentials. While firms like Two Sigma managed to detect and contain the attempt with no data compromised, the event sent a shockwave through the financial sector. Regulators like FINRA quickly issued alerts to member firms. It highlighted a stark reality: even organizations with the most mature cybersecurity budgets remain vulnerable to social engineering when human voices can be convincingly faked in real time. Why Financial Firms are Uniquely at Risk Vishing works because it targets the gaps that software cannot easily monitor. Email security platforms inspect links and attachments, but they have zero visibility into an incoming phone call. In hedge funds and private equity firms, three distinct factors make voice phishing particularly dangerous: Concentrated Authority: Small, tight-knit teams often handle massive capital flows. A single treasury analyst might have the clearance to initiate wire transfers that would require multiple levels of corporate sign-off elsewhere. A Culture of Urgency: Fast-paced financial markets mean out-of-band, high-priority requests from senior leadership are regular business, not an anomaly. When a voice sounding identical to the CFO demands an urgent transfer, the natural instinct is to execute quickly. Overworked IT Help Desks: Attackers often target internal support teams under the guise of an executive locked out of their account. A single MFA reset granted over the phone gives attackers direct entry to identity layers without ever touching a managed endpoint. Traditional security advice often suggests procedural callbacks: hanging up and calling the person back on a pre-registered internal extension. While effective on paper, callbacks fall apart when attackers spoof caller IDs, target personal mobile devices, or leverage urgent scenarios where traditional verification feels burdensome. The Missing Link: Instant, Zero-Trust Voice Verification When an attacker can mimic tone, pitch, cadence, and even the background noise of an executive's office, relying on human ear recognition is a losing strategy. This is where dedicated verification layers come in. Tools like TechJutsu's CallerVerify directly address the blind spot created by AI voice deepfakes. Rather than forcing employees to guess whether a voice is authentic or making them cross-reference contact lists under pressure, CallerVerify introduces a simple, real-time identity check right during the interaction. How TechJutsu's Caller Verify Prevents the Breach Out-of-Band Real-Time Authentication: When an incoming call requests sensitive action—whether it is a password reset, an MFA override, or a multi-million-dollar wire—the employee can trigger an instant verification push through CallerVerify. The caller must verify their identity through a secure, authenticated channel (like an identity provider push notification or biometric check) on their pre-enrolled device. If the caller is an AI clone, they cannot complete the challenge. Closing the IT Help Desk Vulnerability: A classic tactic in the recent hedge fund wave involved callers claiming to be IT staff needing access, or employees requesting a reset from the help desk. TechJutsu CallerVerify standardizes identity confirmation for internal support desks. Help desk agents don't have to evaluate whether the voice "sounds right"; they simply look for the cryptographic verification status on their screen before granting access. Eliminating Caller ID Spoofing Risks: Attackers easily falsify phone numbers to match legitimate corporate contacts. CallerVerify operates outside the telecom network's trust boundary. It verifies the actual identity behind the call rather than relying on phone carrier metadata. Frictionless Compliance for Regulated Environments: With bodies like FINRA scrutinizing how financial institutions handle social engineering risks, having an auditable log of voice identity verifications provides tangible proof that your organization maintains rigorous access controls. Moving Beyond "Hope and Re-train" Training employees to recognize voice phishing remains important, but relying on staff to spot microscopic inconsistencies in a synthetic voice is a gamble. AI audio technology improves every month, making deepfakes nearly impossible to distinguish through raw human listening. The August 2026 attacks against top hedge funds served as a clear warning: the perimeter has shifted to the voice channel. Organizations must treat phone calls with the same Zero Trust philosophy applied to network connections—never trust, always verify. Implementing automated verification solutions like TechJutsu CallerVerify ensures that no matter how convincing an AI voice sounds, unauthorized requests stop before any damage is done. Contact the TechJutsu team today to learn how CallerVerify can help safeguard your organization.

When McDonald’s AI hiring platform, McHire, and its automated chatbot "Olivia" suffered a global data breach, the personal records of over 60 million job applicants were exposed. The root cause was not a complex zero-day exploit. Access was gained through basic authentication failures, including the use of default credentials like123456. As Atturra CEO Stephen Kowal noted following the incident, deploying AI tools without proper data curation and identity governance is like building a mansion on sand. While this breach involved recruitment data, the underlying vulnerability applies directly to enterprise IT. Companies are rapidly deploying AI Virtual Agents to automate help desk requests, employee onboarding, and password resets. The issue is straightforward: AI agents can execute sensitive actions at scale, but they cannot detect impersonation. Without cryptographic identity verification embedded directly into the conversational workflow, AI automation becomes an open target for attackers.   The Risk Profile of AI Virtual Agents   Enterprise IT teams routinely deploy virtual assistants on platforms like ServiceNow to handle routine tasks, such as: Resetting corporate and single sign-on passwords Unlocking user accounts Resetting multi-factor authentication (MFA) tokens Granting temporary access to systems and applications These automated workflows require elevated permissions. If an AI agent relies on static credentials, basic chat context, or traditional security questions (such as employee IDs or dates of birth), attackers can easily bypass them using scraped data or AI-generated voice and text phishing. THE VULNERABLE WORKFLOW Once the virtual agent accepts the unverified prompt, it executes the change in seconds. The organization gets the speed of automation, but with zero identity assurance. The Solution: CallerVerify for ServiceNow AI Agent To secure automated workflows, identity verification must happen in real time before any sensitive action is executed. CallerVerify for ServiceNow AI Agent adds a Zero Trust verification layer to the ServiceNow Virtual Agent. It eliminates security questions by triggeringstep-up multi-factor authentication directly from the chat session, requiring no custom coding and zero manual intervention from support staff. How the Workflow Operates: 1. User Request: An employee asks the ServiceNow Virtual Agent for a password reset, account unlock, or access change. 2. Step-Up Challenge: Before performing the operation, Caller Verify sends a push notification to the user's enrolled device via Okta or Microsoft Entra ID. 3. One-Tap Verification: The user approves the push notification (or completes a number-matching challenge or biometric prompt). 4. Action Executed: The ServiceNow AI Agent verifies the cryptographic confirmation and completes the requested action immediately. 5. Automatic Audit Trail: Caller Verify updates the ServiceNow ticket with the verification method, timestamp, and status, and closes or routes the record automatically. Key Capabilities Built for Enterprise IT CallerVerify for ServiceNow Virtual Agent is built specifically to address the identity gap in automated IT workflows: - Native Multi-Factor Support: Verifies users through existing enrollments in Okta (Okta Verify, FastPass, TOTP, Security Keys) or Microsoft Entra ID. - Reusable Topic Blocks: Pre-built, Natural Language Understanding (NLU) enabled ServiceNow topic blocks that security teams can drop into any Virtual Agent workflow. - Support for ServiceNow Shift Zero: Generates cryptographic evidence for every automated action, satisfying audit and compliance requirements for SOC 2, ISO 27001, and HIPAA. - Securing SOC Escalations: Ensures that when autonomous security systems (such as Tier 2 SOC AI Specialists) escalate remediation tasks, the request originates from a verified employee. - Dynamic Ticketing and Fail-Safes: Automatically logs interaction details. If a user fails the verification step, the session is immediately escalated to a live agent with a security flag. Summary The McDonald's incident demonstrates that security cannot be an afterthought in AI deployments. Automating help desk operations delivers massive efficiency, but only when identity verification is built directly into the foundation. By embedding cryptographic verification into ServiceNow Virtual Agent, enterprises can eliminate impersonation risks, protect sensitive data, and let AI operate safely at scale. Next Steps - Learn more about Caller Verify for ServiceNow. - Install the application directly from the ServiceNow Store. - Contact TechJutsu to review your enterprise IAM and help desk security architecture.

ServiceNow has introduced a bold vision for Autonomous Security called Shift Zero. The idea is straightforward: help security teams move from fragmented, reactive work to a prevention-first model that uses AI to detect, contain, and resolve threats much faster. By bringing exposure management, non-human identity remediation, and Agentic AI Specialists into one AI Control Tower, ServiceNow gives organizations a way to respond in milliseconds instead of minutes or hours. That is a meaningful step forward. It also raises an important question that every autonomous security program needs to answer: What happens when the fastest part of the security system still depends on trusting the person on the phone or in chat? As AI agents take on tasks like credential resets, access changes, and incident response, the human interaction point becomes a real risk. If an attacker can convince a support agent or AI workflow that they are a legitimate employee, speed becomes a liability. To make Shift Zero secure in practice, identity proof needs to extend beyond systems and machine identities into the voice and chat channels where support requests begin.   1. The Machine-Speed Paradox: Why Agentic AI Is a Target for Vishing   ServiceNow’s Autonomous Security architecture introduces specialized AI agents that can handle high-volume workflows such as vulnerability patching, and Tier 2 incident triage. Attackers know that breaking advanced cryptography or compromising hardened cloud infrastructure is difficult. It is often much easier to target people through social engineering. Attack path What happens Attacker or AI voice clone Uses vishing or impersonation to pose as an employee. ServiceNow AI agent or help desk analyst Receives the request and is pressured to act. Autonomous action A credential reset or access change is triggered before identity is cryptographically proven. Result The attacker gains a path to account takeover. A typical help desk scenario looks like this:   A threat actor uses generative AI voice cloning or stolen personal information to contact the support desk or an automated chat agent. They claim to be an executive who is locked out of their account. The support agent or AI workflow relies on knowledge-based authentication, such as an employee ID, manager’s name, or date of birth. The attacker provides answers that are easy to find from public sources or leaked data. The AI agent completes the reset at machine speed.   In this scenario, Shift Zero is compromised. The problem is not the AI’s logic. The problem is that the system does not have cryptographic proof of who is on the other end of the interaction. 2. Closing the Gap: The Human-AI Identity Handshake with CallerVerify   To protect the integrity of the ServiceNow AI Control Tower, human identity verification needs to match the speed and rigor of machine security. Knowledge-based security questions should be removed from high-risk workflows. verification must match the velocity and rigor of machine security. Knowledge-based security questions must be eliminated entirely.   The TechJutsu’s CallerVerify closes this gap. Built into the ServiceNow workspace, CallerVerify replaces security questions with a real-time push notification MFA challenge.  The Caller Verify workflow in ServiceNow How It Works inside ServiceNow: 1. Trigger: When a user contacts support (via phone or chat) requesting a high-risk action, the ServiceNow page loads the CallerVerify. 2. Challenge: The support agent (or automated AI workflow) triggers a push notification to the caller's registered mobile device (e.g., Okta Verify, Microsoft Authenticator). 3. Verification: The user completes a number-matching challenge (e.g., "Tap the number 47 on your screen"). 4. Audit Trail: Once verified, the caller verify automatically updates the ServiceNow case. Custom fields populate with the Verification Method, Time Stamp, and Cryptographic Status. By ensuring that the user is cryptographically verified before the ServiceNow AI Agent executes the ticket, you eliminate social engineering without slowing down the workflow. 3. The Outbound Trust Problem: When Agentic AI Calls the User (OrgVerify) The Shift Zero paradigm doesn't just process inbound requests; Agentic Incident Response proactively reaches out to users. If ServiceNow detects a compromised credential, an automated workflow might initiate an outbound call or message to notify the employee and guide them through remediation. However, recent high-profile support platform breaches have made users rightfully paranoid. If an automated system calls an employee, why should the employee trust it? "I just read about major data breaches in the news. How do I know you're actually my IT department calling, and not a scammer using a spoofed number?" Without outbound verification, users will ignore automated security alerts or refuse to cooperate, crippling the effectiveness of autonomous incident response. The Solution: OrgVerify First Using the same Caller Verify, ServiceNow workflows can initiate OrgVerify before asking the user for any action: 1. Outbound Trigger: The automated ServiceNow system calls the employee regarding an active threat. 2. Agent Code Generation: The OrgVerify generates a time-bound, secure Agent Code (e.g., X-7567). 3. Outbound Proof: The caller reads the code, and the employee inputs it into their OrgVerify Mobile App. 4. Instant Trust: The app confirms: "Verified Identity: Internal IT Security Team." Now, trust is established in both directions. The employee knows the call is authentic, and the system can proceed with remediation. 4. Achieving True "Shift Zero": Continuous Control & Auditability ServiceNow emphasizes that autonomous security must be auditable and governed, delivering proof of what acted, why, and who is accountable. Legacy verification methods (like asking a user their mother's maiden name) create zero compliance evidence. They leave security teams blind during SOC 2, ISO 27001, or HIPAA audits. By embedding CallerVerify and OrgVerify into your ServiceNow architecture, you achieve complete cryptographic governance: - Zero Exposure at the Help Desk: Eliminates the #1 vector for Account Takeover (ATO). - Automated Audit Logs: Every verification event is stored as structured data directly inside the ServiceNow ticket. - Reduced Average Handle Time (AHT): Verification drops from 90 seconds of tedious security questions to <10 seconds of push-button authentication. - Bidirectional Trust: Secures both inbound support requests and outbound automated alerts. Protect the Human Layer of Your AI Control Tower ServiceNow is building the future of machine-speed cybersecurity. But an autonomous system is only as secure as its weakest identity link. Don't let legacy phone verification undermine your investment in Agentic AI and Autonomous Security. Securing the human element requires a cryptographic handshake. Take the Next Step: - Explore the Connector: See how the CallerVerify integrates natively with ServiceNow. - Outbound Authentication: Learn how OrgVerify stops Caller ID spoofing. - Book a Demonstration: Schedule a technical demo with TechJutsu.

We talk a lot about caller verification and best practices in this blog, but what does that actually mean for you and your organization? Here are a few guiding principles to think about when setting up verification for your callers: Don’t use information that can be guessed Yes, this means no security questions. With social media more popular than ever, it’s easy for fraudsters and bad actors to look up information about your callers and impersonate them. If you’re relying on a caller providing their employee number or their cat’s name, you can’t be sure if it’s your caller. Anyone could have looked up that information online. Think twice about biometrics Voice authentication may seem like a simple solution, but not in the new world of AI. Voice authentication is easily phished or faked, whether with AI imitation or a good old-fashioned phishing phone call. Is that really a bad connection, or is someone splicing together a recording of your caller’s voice? Consider device-based factors Since knowledge or biometric factors are not secure, what should you use instead? We recommend device-based factors, such as an authenticator app or code. Using an authentication code or prompt sent to a device the user controls is best. You can set this up by having your callers install an authenticator app and use the app to authenticate. For corporate devices, you can increase the security of this method by requiring the device owner to set up a PIN or passcode to access the verification. Can’t use an authenticator app? A TOTP (time-based one-time pad) code sent to a phone number or email the user controls can be an OK substitute, though there is a risk of compromise if an attacker compromises the caller’s email or SIM (e.g. via a SIM swap). Keep it simple The simpler your verification is, the easier and quicker it will be for callers and call center employees to manage. Surprise and delight your callers by verifying them quicky and easily and helping them move onto the purpose of their call faster. Not only will your callers be more secure, they’ll be happier too! Don’t go it alone Call in some expert help to make your call center verification the best it can be. We’re here at TechJutsu to help set you up with caller verification that keeps you secure and your business moving with Caller Verify. Book a Demo to learn more

Caller Verify isn't just for calls anymore   In the world of cybersecurity, we spend millions on firewalls, encryption, and endpoint protection. But there is one massive security loophole that hackers exploit every single day: The Support Call.   Social engineering, specifically vishing or voice phishing, is on the rise. A hacker calls your IT help desk and pretends to be a frustrated executive who has lost their password. By convincing an agent to reset it, the attacker gains full access to your network within minutes.   Traditional security questions like "What was your first pet’s name?" are no longer enough. Thanks to social media, that information is often public. To truly secure your organization, you need Multi-Factor Authentication (MFA) for the voice channel.   That is exactly where the Caller Verify Universal Connector  comes in.   What is the Caller Verify Universal Connector?   Developed by the identity experts at TechJutsu, the Caller Verify Universal Connector is a Chrome extension designed for help desk agents and support teams. It bridges the gap between your phone system and your Identity Provider (like Okta).   Instead of an agent asking a series of unreliable knowledge-based questions, they can send a secure MFA push notification directly to the caller’s registered device while they are still on the line.   How It Works: Simple, Fast, Secure   The "Universal" part of the name is key. This extension is built to live where your agents work. Whether they are using ServiceNow, Salesforce, Zendesk, or a custom internal CRM, the connector sits ready in the browser.   The Call Comes In:  An employee or customer calls requesting a sensitive action (password reset, account change, etc.)   The Agent Pulls up the user:  The agent uses their CRM tool to find the caller's profile. The Caller Verify extension automatically loads the user's profile.   The Agent Triggers Verification:  The agent uses the Caller Verify Universal Connector to trigger a push notification to the caller.  4. The Push Notification:  The caller receives an Okta Verify prompt on their phone.   Instant Confirmation:  Once the caller taps "Yes," the agent sees a "Verified" status in real-time.    No more guessing, no more interrogation, and most importantly, no more unauthorized access.   Why Your Organization Needs It   1. Eliminate Knowledge-Based Authentication Knowledge-Based Authentication is increasingly unreliable in the age of social media and large-scale data breaches. Caller Verify replaces these weak questions with cryptographically secure verification, significantly reducing the risk of fraud.   2. Reduce "Average Handle Time" (AHT) Asking three or four security questions takes time. Often, users forget their answers, leading to frustration. Sending a push notification takes seconds. This extension makes your support team more efficient and your users happier.   3. Audit Trails & Compliance For companies in regulated industries (like Finance or Healthcare), proving who  authorized a password reset is vital. Caller Verify creates a logged event in your identity provider, giving you a clear audit trail for every single verification.   4. Zero-Friction Integration Because it is a Chrome extension, there’s no massive software overhaul required. It’s lightweight, easy to deploy across a fleet of support laptops, and works "universally" alongside your existing web-based tools.   The Bottom Line   The help desk is often the "soft underbelly" of an organization's security posture. The Caller Verify Universal Connector hardens that target, bringing Zero Trust principles to the voice channel.   If you’re ready to protect your team from social engineering and streamline your support calls, it’s time to move beyond security questions.   Download the Caller Verify Universal Connector on the Chrome Web Store today.

Microsoft Teams has become the backbone of modern workplace collaboration. From quick hallway-style chats to full executive meetings, Teams calls are now trusted as a legitimate and secure communication channel. Unfortunately, attackers know this too.   Social engineering has evolved beyond suspicious emails and phishing links. Today, threat actors are actively targeting employees through Teams voice and video calls, impersonating IT staff, executives, or trusted vendors. This makes verifying callers in Teams calls a critical and often overlooked security practice.   In this post, we’ll explore why caller verification matters, how attackers exploit Teams calls, and what employees can do to protect themselves and the organization.   The Rise of Voice-Based Social Engineering in Teams  Most employees are trained to be cautious with email. We look for suspicious links, double-check sender addresses, and report phishing attempts. Calls, however, feel more legitimate.   Attackers exploit this trust by: Posing as IT support claiming there’s an urgent account issue Impersonating a manager or executive who “needs something quickly” Pretending to be a vendor or Microsoft partner assisting with a problem   Because Teams displays a name and profile photo, employees may assume the caller is genuine even when the account is compromised or misleadingly named.   Unlike email, voice calls add pressure. Attackers rely on urgency, authority, and confusion to bypass normal verification steps.   Why Teams Calls Are Especially Effective for Attackers  Microsoft Teams is trusted, internal, and fast-paced. That makes it an ideal tool for social engineering.   Here’s why these attacks work so well: Minimal friction: Accepting a call takes one click Familiar interface: Employees assume internal calls are safe Real-time interaction: There’s no time to “think it over” like with email Psychological pressure: It’s harder to say “no” to a live person   Once trust is established, attackers may ask for: Multi-factor authentication (MFA) approval Password resets or temporary codes Installation of remote access tools Sensitive company or personal information   At that point, damage can happen very quickly.   The Real Risk: It Only Takes One Call   A single successful Teams call scam can lead to: Account takeover Data exfiltration Internal lateral movement Financial fraud Reputational damage   Even organizations with strong MFA and email protection can be compromised if employees are tricked into approving access over a call. That’s why verifying the caller must become standard behavior just like verifying suspicious emails.   Introducing Caller Verify: The Solution for MS Teams Verification shouldn't be a guessing game based on a profile picture or a display name. Our latest video demonstrates how the Caller Verify Universal Connector bridges the security gap by integrating identity providers like Okta directly into your Teams experience.   How Modern Verification Works The process is designed to be seamless for the user while providing ironclad security for the organization: Initiation: While in a Teams chat or call, the administrator or employee opens the Universal Connector. Identity Check: The tool automatically identifies the contact and triggers a verification request. MFA Challenge: The caller receives a push notification (e.g., via Okta Verify) on their mobile device. They must approve it using biometric data like Face ID or a fingerprint. Audit Trail: Once verified, a success message is generated. This can be copied directly into the Teams chat, creating a clear, timestamped audit trail of the identity check.   Why It Matters for Your Business Implementing a caller verification protocol isn't just about stopping one bad actor; it's about building a culture of security. Confidence for IT Admins: Before granting permissions or resetting passwords, admins can be 100% sure they are talking to the right person. Compliance & Auditing: Every verification creates a record, ensuring your organization meets security standards and internal compliance requirements. User Empowerment: When employees know that caller verification is a standard part of company policy, they are less likely to fall for high-pressure social engineering tactics.   Watch the Process in Action Security doesn't have to be complicated to be effective. To see exactly how the Caller Verify Universal Connector works within the Microsoft Teams interface, watch our full walkthrough here: Caller Verify Universal Connector: Secure Identity Verification in Microsoft Teams   If a request feels unusual, urgent, or out of character stop and verify. A few extra seconds can prevent a major security incident.   Get started with the Caller Verify Universal Connector for Teams today. Contact the TechJutsu team now.

Security researchers at Arctic Wolf and Fortinet have confirmed a critical situation: a new vulnerability allows attackers to bypass authentication on FortiGate firewalls via the FortiCloud SSO service.  The immediate advice from Fortinet is drastic but necessary:  Disable FortiCloud SSO immediately.   While this stops the technical bleeding, it creates a new, dangerous operational gap, one that social engineers are already preparing to exploit.  The "Break-Glass" Vulnerability  When you disable Single Sign-On (SSO) for your network infrastructure, you are effectively locking the front door to your own house. To get back in to manage devices, apply patches, or monitor traffic, your network administrators must revert to "break-glass" procedures.  They have to use  local administrative accounts  (e.g., admin, root) that are not tied to their personal identities.  This creates chaos. Admins who are used to clicking one button to log in are now locked out. They need passwords they haven't used in months. They are under pressure to secure the network.  This is the exact moment fraudsters strike.   The Scenario: The "Panicked Admin" Call   Attackers read the same threat intelligence reports we do. They know that right now, in Operations Centers across the globe, SSO is being disabled and confusion is high.  Expect your Help Desk to receive calls like this:  "Hi, this is Dave from Network Engineering. Look, we disabled SSO per the Fortinet advisory, but now I’m locked out of the Edge Firewall. I need the local admin password immediately to apply the mitigation before we get hit. Hurry."   To a helpful agent, this sounds plausible. It sounds urgent. It sounds like a security priority.  But if that caller isn't Dave, and your agent reads out the local admin password,  the attacker has won.  They didn't need a technical exploit; they just needed to exploit the chaos caused by one.  When Tech Fails, Verification Must Hold  This incident highlights a critical truth:  Technology breaks.  Firewalls have bugs. SSO services have vulnerabilities.  When the technical layers fail, your security falls back to the human layer. If your method of verifying that human is weak (like checking Caller ID or asking "secret" questions), your last line of defense is gone.  This is where TechJutsu’s Caller Verify  becomes your safety net.  How to Secure the Patch Gap   Even when your infrastructure is vulnerable, your verification process doesn't have to be. Here is how Caller Verify protects your organization during the Fortinet crisis:  Verify the Person, Not the Login:  Even if the "admin" claims they can't log in to the firewall, their trusted mobile device is still active. When they call for support, the agent triggers a Caller Verify push notification.  Cryptographic Certainty:  The real admin taps "Approve" on their device. A fraudster spoofing their number cannot do this.  Gatekeep the Keys:  The agent sees a green "Verified" light  before  they even consider releasing local credentials or "break-glass" passwords.  Audit the Chaos:  Every verification attempt is logged in ServiceNow. If an attacker tries to impersonate your admin, you have a digital record of the failed attempt.  This record is valuable intelligence during an active incident.  Don't Let a Patch Become a Breach   The Fortinet vulnerability is a technical problem, but fixing it is an operational challenge. As you move to disable SSO and lock down your perimeter, ensure you aren't leaving the phone line wide open.  Technology breaks. Trust shouldn't.   Is your Help Desk ready for the "Panicked Admin" call?  Book a demo with Caller Verify today.

Last week, Las Vegas hosted one of the largest enterprise technology events of the year: ServiceNow Knowledge 2025 . With more than 25,000 attendees from around the globe, this year's conference was an incredible showcase of innovation, insight, and community. The theme, “Put AI to Work for People – Now,” set the tone for three packed days focused on workflow automation, AI integration, and digital transformation, all driven by ServiceNow’s rapidly evolving platform. We were thrilled to have Ajay from our team on the ground, representing our company and our flagship product, Caller Verify . Caller Verify seamlessly integrates with ServiceNow. It is already helping customers eliminate impersonation attacks and improve call center efficiency. First Impressions: Bigger, Bolder, Smarter Ajay described Knowledge 2025 in one word: huge . The scale of the conference, with thousands of IT leaders, developers, ServiceNow users, and ecosystem partners under one roof, signaled that digital workflows and AI-enhanced service delivery are central to enterprise strategy in 2025. The event wasn’t just about flashy product demos or grandiose keynotes. It was about real knowledge sharing. Companies of every size and from various industries came to share practical experiences, valuable lessons, and creative uses of the ServiceNow Platform. This spirit of collaboration makes Knowledge unique and invaluable. Connecting with Old and New Clients One major benefit of attending Knowledge 2025 was the opportunity to meet face-to-face with current and prospective customers. Ajay connected with several of our existing clients, strengthening relationships. He heard first-hand how they are deploying Caller Verify to boost service desk security and meet compliance standards. Translating online conversations into in-person connections can be tricky. At one point, Ajay struck up a conversation with a fellow attendee during breakfast. After a few minutes, they realized they had met on a video call weeks earlier! It turns out that matching three-dimensional people to their flat video call personas isn’t always easy. Ajay also spoke with representatives from well-known companies assessing our solutions. Some are on track to become clients soon. With organizations recognizing the urgency to protect help desks and call centers against impersonation and social engineering attacks, Caller Verify is becoming an essential tool in the ServiceNow ecosystem. A Seamless Integration with ServiceNow As a proud ServiceNow partner , TechJutsu offers solutions that integrate directly into the workflows organizations already use. Caller Verify works natively with ServiceNow, enabling help desks to validate user identities in real-time. It uses strong, out-of-band authentication within existing incident management and service workflows. Our partnership with ServiceNow ensures that our clients receive cutting-edge security solutions and a smooth, unified user experience. A Touch of Vegas Glam Of course, it wouldn’t be Vegas without a little showbiz sparkle. Knowledge 2025 delivered with a performance by Gwen Stefani at the Knowledge After Party. This breathtaking event took place at the Sphere venue. It was a high-energy, high-tech celebration wrapping up a week focused on the future of work and the role AI and automation play in shaping it. The Future is Bright Reflecting on TechJutsu’s experience at Knowledge 2025 confirms what we've long believed: workflow-integrated identity verification isn’t just a "nice to have." It’s essential. With Caller Verify, we help organizations close critical security gaps in their service desks and call centers while ensuring a fast, user-friendly experience aligned with the ServiceNow ecosystem. Final Thoughts Whether you attended in Las Vegas or followed from afar, one thing is clear: the ServiceNow community is now bigger, smarter, and more energized than ever. Don’t let impersonation be your weak link. Let's put identity security to work! To learn more about Caller Verify, Book a demo with us today.

In today's digital security landscape, there is an attack vector that is quietly growing in both scale and effectiveness. Vishing leverages phone calls to impersonate trusted sources, often using only psychological manipulation to extract sensitive information. What’s worse, it often bypasses technical protections entirely. The Clorox Service Desk Case: A Cautionary Tale A revealing case highlighted by Ars Technica underscores the shocking simplicity of some attacks. In this breach, compromised customer service agents at Clorox handed over passwords and access to internal systems without the attackers using malware or elaborate hacking tools. The attackers simply asked! The company has since sued its service desk vendor, arguing that the incident was preventable had standard verification protocols been in place. This case demonstrates that even multi-million-dollar cybersecurity stacks can be undermined through phone-based social engineering, especially when vetting policies are lax or inconsistently enforced. Why Vishing Is So Effective Caller ID Spoofing : Using VoIP technology, attackers can make their phone number appear familiar or official, increasing legitimacy during a call. Social Engineering Prep : Attackers comb social media and corporate directories to glean details like employee names, job roles, or company org charts to make their deception more convincing. Timely Simplicity : With vishing campaigns, hackers don’t need advanced software or system exploits. A well-crafted phone call can bypass security altogether. As seen in the Clorox case, simply “asking” may be enough. Famous Vishing Attacks You Should Know Twitter (2020) : Attackers used "phone spear phishing" to impersonate internal helpdesk staff. By misdirecting employees, they gained access to internal tools and hijacked verified Twitter accounts, launching fraudulent cryptocurrency scams. Other Industries : Similar tactics have been reported at banks, cryptocurrency exchanges, and hosting companies. Simple voice-based impersonation without breaching any firewall. Four Steps to Protect Yourself from Vishing Train Your Staff on social engineering awareness, especially help desk personnel, who are primary attack targets. Avoid Knowledge-Based Authentication : Do not ask for easily found details like birthdates or employee IDs. Use Out-of-Band Verification : Implement MFA push notifications to a registered device to confirm caller identity by requiring interaction outside the phone call. TechJutsu’s Caller Verify enables your existing MFA for this purpose. Flag and Escalate High-Value Accounts : For executives or IT admins, require manager approval or elevated verification steps. Vishing: A Human Vulnerability In many organizations, phone calls remain one of the least secured channels. While email phishing attempts can be detected by spam filters and gated landing pages, vishing preys entirely on trust and social engineering . As ChatGPT and other voice synthesis tools improve, even convincing impersonations can be generated with minimal effort. The Psychological Aspect of Vishing Understanding the psychology behind vishing is crucial. Attackers exploit human emotions, such as fear, urgency, and the desire to help. They create scenarios that compel individuals to act quickly without thinking critically. This psychological manipulation is what makes vishing so dangerous. Real-World Implications of Vishing Attacks The consequences of vishing attacks can be severe. Organizations may suffer financial losses, reputational damage, and legal repercussions. Moreover, sensitive data can be compromised, leading to further security breaches. It is essential to recognize that the impact of vishing extends beyond immediate losses; it can affect long-term trust and relationships with customers and partners. Conclusion: Don’t Let a Simple Call Lead to Catastrophe The Clorox incident is a stark reminder that sometimes hackers don’t need to exploit software. Often, they prey upon our human willingness to help. Vishing may sound low-tech, but its impact is real: compromised credentials, stolen data, and unauthorized access delivered through a mundane phone call. By implementing strict verification protocols, leveraging multi-factor authentication, and elevating threat awareness within help desk teams, organizations can protect themselves from voice-based scams. In the war against cyber threats, the weakest link is not malware; it is trust. Stay cautious, stay curious, and always verify the caller. To book a demo of our Caller Verify solution, contact us today! Resources: Canadian Centre for Cyber Security

The IT help desk is the nerve center of an organization. It's the trusted resource for employees needing access, support, and problem-solving. However, this trusted position also makes it a primary target for cybercriminals. Attackers know that if they can compromise the help desk, they can gain a foothold into the entire organization. Here are the biggest security risks every modern help desk faces today. Understanding the Risks 1. Social Engineering and Impersonation This is, by far, the most prevalent and effective threat. Attackers often call the help desk pretending to be an employee, frequently one who is traveling or a high-level executive. They use urgency and pressure to trick an agent into resetting a password or granting access to systems. This attack, known as "vishing" (voice phishing), bypasses technical defenses by exploiting the human element. The recent high-profile attacks by groups like Scattered Spider almost always begin with a simple, manipulative phone call to the help desk. 2. Inadequate and Outdated Authentication The primary defense against impersonation is authentication, but many help desks still rely on dangerously weak methods. Knowledge-Based Authentication (KBA): Security questions are no longer secure. The answers are easily found on social media or in data breaches. NIST specifically calls out KBA as insufficient. Relying on Caller ID: Caller ID can be easily "spoofed," making it trivial for an attacker to appear as if they are calling from a legitimate employee's phone number. 3. Insider Threats A security risk can also come from within. While malicious employees who intentionally abuse their access are a concern, a far more common risk is the unintentional insider threat. This is a well-meaning but negligent employee who makes a mistake. For example, an agent might be tricked into bypassing protocol, or an employee could write their password on a sticky note. These actions, while not malicious, create openings that external attackers are quick to exploit. To avoid this, it is important to have controls implemented by technology that do not depend on an overly helpful help desk agent’s judgment. 4. Lack of Continuous Security Training Many organizations provide security awareness training during onboarding but fail to follow up. The threat landscape changes constantly, with attackers developing new social engineering tactics. Without regular, specific training on recognizing vishing attempts and the importance of following protocol, agents can easily fall victim to a well-rehearsed attacker. The Common Thread: The Identity Problem Nearly all of these major risks boil down to one fundamental challenge: the inability to reliably verify a caller's identity. Without a quick, secure way to prove a caller is who they claim to be, your help desk is forced to rely on guesswork, weak data points, and the hope that an agent can outsmart a professional scammer. How to Mitigate These Risks Securing the help desk starts with solving the identity problem. Implementing a real-time, Multi-Factor Authentication (MFA) process is the single most effective step you can take. By requiring users to approve a request on a trusted device they own, you remove the agent's burden and the attacker's advantage. This hardens your primary point of entry and provides a strong defense against the most significant threats you face. It is also critical to enforce strong verification. This can be accomplished with business rules that don’t allow a help desk agent to progress with the ticket until the verification is complete. Conclusion Don't let your help desk be your weakest link. Talk to our team to discover how to secure it with Caller Verify. By addressing these vulnerabilities and implementing robust security measures, organizations can significantly reduce the risks associated with their help desks. Remember, a secure help desk is a secure organization.

In the world of call center management, Average Handle Time (AHT) is a critical metric. The goal is always to resolve a customer's issue as efficiently as possible. Because of this, security measures are often seen as a necessary evil.  All too often people want to avoid this cumbersome process that adds friction and slows agents down.  But what if the  right  kind of security could make your calls shorter and more efficient?  That’s the reality of moving from outdated verification methods to modern, real-time authentication. Poor authentication is a primary driver of high AHT, while a streamlined process can significantly reduce it.  How Traditional Verification  Increases  AHT   Consider how traditional verification methods actively inflate AHT. The process is a script of inefficiency:  The Knowledge-Based Authentication (KBA) Interrogation:  Agents must spend the first 30-90 seconds of every sensitive call asking a series of security questions.  The Forgotten Answer:  Legitimate customers frequently forget the exact format of their answers, leading to failed attempts, repeated questions, and rising frustration.  Costly Escalations:  When a customer fails the KBA process, the agent must escalate the call or follow an even longer, more complex manual identity-proofing procedure, bringing resolution to a halt.    Every one of these steps adds seconds, or even minutes, to the call, frustrating both the agent and the customer.  How Modern Authentication  Reduces  AHT   Now, contrast the old way with a modern, MFA-based workflow.  The Request:  The caller asks for a password reset.  The Trigger:  The agent clicks a button to initiate verification.  The Approval:  A push notification appears on the user's phone, and they tap "Approve."  The Confirmation:  The agent's screen shows "Verified" in seconds.  The   Documentation: This is all auto logged in the Service ticket, without human effort  The entire security process is completed in less time than it takes to ask one security question.  This approach slashes AHT in several ways:  Eliminates the KBA Script:  You can remove the entire interrogation sequence from the call flow.  Reduces Errors and Escalations:  There are no wrong answers to forget. The verification is a simple yes/no, drastically cutting down on failed attempts that require manager intervention.  Gets to the Point Faster:  Agents can immediately start working on the caller's actual problem, leading to quicker resolutions.  Improves Customer Experience:  A faster, smoother process at the start of the call leads to a happier customer, which makes the rest of the interaction more efficient.  By implementing a solution like Caller Verify, you're not choosing between security and efficiency. You're using better security to  drive  better efficiency. It’s a strategic upgrade that strengthens your defenses while simultaneously improving a core operational metric.  Want to improve security and performance at the same time?  Book a demo to see how.

The recent CrowdStrike incident led to widespread system failures and put a spotlight on the critical need for robust identity verification methods. As organizations grapple with the aftermath, one pressing issue is the management of BitLocker recovery key requests. With systems down and traditional identification methods like knowledge-based factors proving insufficient, IT teams face a unique challenge. How can IT departments confidently confirm that callers are who they claim to be? Providing elevated access with admin credentials or BitLocker keys is a highly sensitive operation that increases security exposure and should only be permitted when callers are securely identified. The Challenge of Non-Functional Systems The CrowdStrike incident has rendered many computers non-functional, presenting a significant obstacle for identity verification. Typically, IT departments might use the affected device itself as a part of the verification process—such as sending a verification code to the device or requiring a specific action to be taken on it. However, with systems down, these methods are no longer viable. This situation necessitates alternative approaches to ensure secure and reliable identification. The Limitations of Knowledge-Based Authentication Traditionally, knowledge-based authentication (KBA) methods, including passwords and security questions, have been a cornerstone of IT security. However, these methods are increasingly viewed as inadequate. The reasons are multifaceted: Data Breaches and Information Availability : The prevalence of data breaches has made it easier for attackers to access personal information, including answers to common security questions. Publicly available data and social media profiles further exacerbate this issue, making it relatively easy for attackers to impersonate legitimate users. Password Weaknesses : Passwords are often weak, reused across multiple platforms, or stored insecurely. These vulnerabilities are well-known and frequently exploited by attackers. Additionally, passwords alone do not provide adequate protection against sophisticated phishing attacks or social engineering tactics. Given these limitations, relying solely on KBA for verifying requests for BitLocker recovery keys is risky. Organizations need more secure, multi-layered approaches. Multi-Factor Authentication (MFA) Multi-Factor Authentication (MFA) is a more robust solution that addresses many of the shortcomings of KBA. MFA requires users to provide two or more verification factors from different categories: Something you know : A password or PIN. Something you have : A hardware token, a mobile device, or an email account for receiving verification codes. Something you are : Biometric data, such as fingerprints or facial recognition. By requiring multiple forms of verification, MFA significantly reduces the risk of unauthorized access. For instance, even if an attacker knows a user's password, they would still need access to the user's mobile device or biometric data to proceed. This layered security approach makes it much harder for attackers to compromise an account. Call Center Authentication Strategies When dealing with sensitive information like BitLocker recovery keys, it is crucial to use secure communication channels. This means avoiding insecure methods like standard email or unverified phone calls. Instead, organizations should use encrypted messaging services or secure portals that require user authentication. An increasingly common strategy is the use of out-of-band authentication methods. In situations where a caller needs to be verified, rather than requesting information via that voice call, the help desk can send a push notification  to a registered mobile device. Such push notifications provide a secure way for callers to quickly and easily confirm their identity, as they typically require real-time interaction and physical access to a user’s device, making it difficult for attackers to intercept or spoof the authentication process. Call-back verification is another effective technique. After receiving a request for a recovery key, IT support can call the user back using a pre-registered phone number. This method adds an extra layer of verification, ensuring that the person making the request is indeed the authorized user. It also provides an opportunity to verify other information, such as recent activities or specific security questions. The downside of call-back verification is that it is extremely time-consuming and is not automatically logged in the ITSM. Use of Pre-Registered Verification Information Organizations should leverage pre-registered information that only the legitimate user would know or have access to. This can include: Pre-set security questions : These should be unique and not easily guessable based on publicly available information. Codewords or passphrases : These are agreed upon during account setup and are not used elsewhere, providing an additional layer of security. Secondary email addresses or phone numbers : These can be used to send verification codes or to confirm the identity of the caller. It is important to regularly update this information and ensure that users are aware of its importance in the verification process. Logging and Monitoring             Every request for a BitLocker recovery key should be meticulously logged and monitored. This includes recording the time, date, identity of the requester, and the IT personnel involved. Monitoring these logs helps identify suspicious activities and potential unauthorized attempts to access recovery keys. Regular audits of these logs are essential. They ensure that all requests are legitimate and comply with security protocols. In the event of a security incident, these logs can provide critical forensic evidence to help identify and mitigate the threat. Logging can be automated with Caller Verify, which logs every verification in the ITSM. Training and User Awareness Finally, training and user awareness are critical components of a comprehensive security strategy. Users should be educated on the importance of securing their accounts and the risks associated with sharing sensitive information. They should also be familiar with the organization's verification processes and know what to expect when requesting a BitLocker recovery key. Users should be encouraged to use strong, unique passwords and to enable MFA wherever possible. Regular security training sessions can help keep users informed about the latest threats and best practices for protecting their information. Conclusion: Evolving Security Practices The CrowdStrike crisis highlights the need for robust and evolving security practices. As threats become more sophisticated, organizations must adopt more advanced methods to verify identities and protect sensitive information. Relying solely on knowledge-based factors like passwords and security questions is no longer sufficient. Instead, a combination of MFA, secure communication channels, call-back verification, and careful logging and monitoring should be used. By implementing these measures, organizations can protect against unauthorized access to BitLocker recovery keys and other sensitive information. In doing so, they can safeguard their data, maintain their reputation, and ensure the trust of their users, even in the face of significant technical challenges. To learn more, Book a demo  with us today.