Enterprise Account Executive - West

Teleskope Identity View: see everything an identity can reach. Identity View lists every human and non-human identity with access to your data, ranked by sensitivity, with full drill-down and one-click CSV export. August 13, 2026 ON THIS PAGE TL;DR: The identity team flags an account. A string of failed logins, then a successful one from a location the employee has never signed in from before. They lock the account and send the data team one question: what could this person have actually touched? Answering that today means logging into whatever app holds the sensitive data and pulling permissions by hand, and non-human identities like service accounts rarely get the same scrutiny when something similar happens to them. Teleskope's new Identity View gives you a searchable list of every identity with access to your data, human and non-human alike, and a full sensitivity-ranked breakdown of what each one can reach, exportable in one click, without leaving the platform. See every identity that touches your data, human and non-human, in one list. Identity View gives you a centralized, searchable list of every identity with access to data across your connected sources, starting with Google Drive and SharePoint. That list is built around two identity types from the start, not as an afterthought. Human identities are the users you would expect, identified by email address. Non-human identities, the service accounts, bots, and integrations that hold access without being tied to any person, get the same visibility in a dedicated view of their own. For each identity, human or not, you see its type, the number of resources it can reach, and the maximum sensitivity of anything in that scope. Human identities also show a trust level (internal, external, or personal), automatically classified based on your organization's configured domains, so a contractor's Gmail address and a colleague's corporate email are never lumped together in the same bucket. Sorting by max sensitivity is where the real value shows up, and it matters just as much for a service account as it does for a person. A flat list of hundreds or thousands of identities becomes an immediate priority queue. You are no longer guessing which accounts, human or automated, deserve a closer look. The identities with the broadest reach into your most sensitive data surface to the top on their own, regardless of whether there is a person behind them. Go from a name, or a service account, to a full access picture in one click. Clicking into any identity opens a full breakdown of what it can reach, and the depth is the same whether you are looking at a person or a piece of infrastructure. You get a sensitivity rollup across critical, high, medium, and low, the specific data elements involved (SSNs, credit card numbers, and similar), the broader data categories in scope (PII, PHI, PCI), and a complete table of every resource tied to that identity, down to the connector, file path, and sharing type. That sharing type, whether access is Direct, Domain, Group, or Organization, applies to human and non-human identities alike, so you can tell at a glance whether a resource was shared with one account specifically or opened up to an entire domain, group, or organization. Non-human identities get their own detail page built the same way, so a service account gets the same rigor of review as an employee, not a lighter-weight summary. From there, you can export the full resource list as a CSV, so the identity's complete access footprint, human or non-human, is ready to hand to legal, HR, or an incident response team without anyone re-running the same lookup in another tool. The blind spot most tools still miss. Non-human identities deserve this level of attention because they are quietly becoming one of the largest sources of unmanaged access in most environments. Every new integration, automation, and bot gets provisioned with access to do its job, and unlike an employee, nobody runs an offboarding checklist when that access is no longer needed. These accounts do not show up in an HR system or an org chart, which means they are also the accounts least likely to get reviewed in a manual audit. Identity View treats registration of these accounts as a first-class workflow, not a side feature. Teams can register known service accounts, bots, and integrations directly in settings, at which point they move out of the human identity list and into a dedicated non-human identities view with the same sensitivity rollups, resource counts, and drill-down detail as any person. For organizations with AWS, IAM roles and users can be included in that same view as a premium add-on, so cloud infrastructure principals sit alongside your SaaS service accounts rather than living in a separate tool entirely. The result is a single place to answer "what can reach our sensitive data" that does not quietly exclude the accounts most likely to be forgotten. The value compounds as your identity landscape grows. A domains view rounds out the picture by grouping human identities by email domain, which is the fastest way to answer a common question during vendor or contractor reviews: how much access does this outside organization actually have across its environment? Security is never a one-time cleanup. Access changes daily as people join, leave, and change roles, and as new integrations and service accounts get connected. Identity View is built for that pace, giving you a living, current picture of who and what can reach your sensitive data rather than a snapshot that goes stale the day after an audit. If your team is still stitching together identity and access answers by hand, it is worth seeing what a single, sensitivity-ranked view of every identity in your environment can do for your remediation time. Book a call to see Identity View in action.

Teleskope launches on the Slack App Marketplace, reinforcing position as leading DSPM platform with native remediation. New integration detects and resolves sensitive data across every Slack message, file, canvas, and list, live and historical, under a guaranteed two-second SLA, with no separate console and no workflow change for employees. July 15, 2026 14:41 ET | Source: Teleskope New York, NEW YORK, July 15, 2026 (GLOBE NEWSWIRE) - Teleskope, the agentic data security platform that resolves data exposure instead of just flagging it, today announced Teleskope for Slack, a native integration now live on the Slack App Marketplace. The integration discovers, classifies, and remediates sensitive data across every message, file, canvas, and list, in real time and across content that existed in Slack before the integration was installed. Slack has become core communication infrastructure for organizations of every size. Until now, security teams have had no native way to enforce data policy at the point a message or file is created inside it. Most tools built for Slack detect a problem and send an alert. None of them close the loop. Native Slack DLP, available only on Enterprise Grid, can tombstone content, but depends on manual policy authoring, has no machine-learning-driven classification, and has no way to scan what is already sitting in the platform. Teleskope brings the same automated remediation to Slack that it applies everywhere else. Real-time detection, native enforcement, and a full audit trail, without an external ticketing loop or a separate console. Detection, notification, and tombstoning all happen inside Slack itself, the same place the message was sent. Policies are not limited to a binary block or allow. A policy can tombstone content outright, or notify the sender and require a business justification before the content is released, putting judgment back into the workflow instead of a hard stop. Historical discovery scans messages, files, canvases, and lists that already existed in Slack before Teleskope was installed, not just risk created going forward. * Product: Teleskope for Slack, a native integration on the Slack App Marketplace. * Company: Teleskope, headquartered in New York City. Website: teleskope.ai. * Categories: Primary Data Security Posture Management (DSPM). Secondary Data Loss Prevention (DLP). * Founded: 2022, by Elizabeth "Lizzy" Nammour, former Airbnb data security engineer. * Coverage: messages, files, canvases, and lists, both live and historical, on Slack Enterprise Grid. * Service level: under two seconds, guaranteed, for detection and remediation. * Customer proof point (Ramp): 100 percent of remediation workflows automated, roughly one hour a week of active management across 44 policies spanning Slack and Google Workspace. * Funding: $25 million Series A in 2026, led by M13, with Primary Venture Partners and Lerer Hippeau. Over $32 million raised to date. * Customers include: Ramp, Chevron Phillips, Notion, Polymarket, Alloy, EarnIn, Aprio. Built for Security Teams, Invisible to Everyone Else Ramp uses Teleskope across both Slack and Google Workspace, enforcing their policies in real time. When Ramp moved its data security workflows onto Teleskope, the transition required no retraining and no change to how employees used Slack day to day. "The lift and shift was so seamless that users didn't even realize we had changed platforms," said a security leader at Ramp. "I've been in the DLP space for a long time and tested a lot of providers. Teleskope is the latest and greatest. They built exactly what we needed, moved fast, and continue to deliver at Ramp's pace," the security leader added. Availability Teleskope for Slack is available today on the Slack App Marketplace for Slack Enterprise Grid customers. "Our customers told us the same thing in different words: they didn't want to train their internal users on yet another tool, they wanted the risk handled where the work already happens," said Elizabeth "Lizzy" Nammour, founder and CEO of Teleskope. "Teleskope for Slack takes the same remediation we run everywhere else and puts it directly inside the tool people use all day." About Teleskope Teleskope is an agentic data security platform that automatically resolves data exposure, not just finds it. Powered by the Data Reasoning Layer, Teleskope continuously discovers sensitive data, determines the appropriate action based on each customer's policies, and enforces that action natively across on-premises, cloud, SaaS, and AI environments. Teleskope competes in the Data Security Posture Management (DSPM) and Data Loss Prevention (DLP) categories. Customers include Ramp, Chevron Phillips, Notion, Polymarket, Alloy, EarnIn, Aprio. Teleskope was founded in 2022 by Elizabeth "Lizzy" Nammour, a former Airbnb data security engineer, and is headquartered in New York City. The company is backed by Primary Venture Partners, M13, and Lerer Hippeau, and raised a $25 million Series A in 2026. Teleskope Platform Reference Platform Capabilities: * Continuous discovery and classification across cloud, SaaS, on-premises, and AI environments * Context-aware classification engine (built on a hierarchical multi-head architecture) * Prism document intelligence (classifies full documents by type and intent rather than field-level scanning) * Data Reasoning Layer (Understand, Decide, Enforce) * Native automated remediation: inform, redact, quarantine, revoke access, relocate, encrypt, delete * Policy Builder and Policy Ingestion (converts existing governance documents into enforceable workflows) * AI Search (natural-language querying) * Real-time data security across Slack, OpenAI, and Claude * Audit-grade logging with full event traceability * Reversible actions with rollback to prior state Industries Served: Financial services, fintech, professional services, advisory, healthcare, technology, hospitality, manufacturing, media, food and beverage, retail. Deployment Options: * Single-tenant Software-as-a-Service (SaaS) * Self-hosted in customer's cloud environment (Bring Your Own Cloud) * Air-gapped deployment Compliance and Regulatory Frameworks Supported: GDPR, CCPA, DPDP Act (India), HIPAA, PCI-DSS, SOC 2, ISO 27001, EU AI Act, ISO 42001. Additional Resources * Teleskope website: https://www.teleskope.ai * Teleskope for Slack listing: https://slack.com/marketplace/A058D3LKPN0-teleskope-enterprise-data-protection * Ramp customer case study: https://www.teleskope.ai/case-studies/how-ramp-achieves-real-time-data-redaction-with-teleskope * Teleskope on LinkedIn: https://www.linkedin.com/company/teleskopeai/ Press Inquiries

Two ways AI agents leak enterprise data, and how to close both. AI agents leak enterprise data in two ways, and the defenses most enterprises already run address only the first. The first is well understood: sensitive data flowing out through the AI pipeline. Someone pastes a customer record or a contract into a prompt, it goes to an external model, and the organization is now trusting that vendor's retention and training policies with it. The second is subtler, and it is the one teams consistently underweight. Agents surface data the user was never supposed to see. An agent queries a source on the user's behalf, and when permissions are even slightly off, which is common, it returns whatever it finds: over-shared drives, stale access, a service account with too much reach. The agent has no model of who should see what, so it surfaces everything within reach. Why the usual fixes leave the same blind spot. The common fixes already in use all leave the same gap. Browser extensions only see the browser, so the moment someone switches to a desktop app, a CLI, or an API, they go blind to most of the real workflow. Network DLP sees the traffic, but it sees TLS-encrypted blobs without the structure to know that a given payload is a customer record with a tax ID in it. Zero-data-retention contracts are mostly reserved for the largest deals, and even with one in place, nothing stops an agent from returning data a user was never allowed to see. Enterprise "no-training" tiers address one risk, but the data still sits with the vendor for up to 30 days, and training was never the main exposure. Full gateways on every device cover the workflow in principle, yet they break on mobile and have to sit on every endpoint, which rarely holds in practice. The deeper issue is that the tools most teams already own were built to scan data at rest. A DSPM scan can tell you, with high confidence, that column 14 of your support database holds Social Security numbers, but it runs overnight and files a report, which does nothing to stop an agent from reading that column into a model's context at 2pm the next day. Agents move data in motion, in real time, faster than any periodic scan keeps up with, so policy has to fire the moment the agent makes the tool call, not in next quarter's audit. Closing both gaps takes two layers working together. Closing this takes control over the pipeline and real-time intelligence on the data flowing through it, working together. * Control over the pipeline decides which sources an agent can reach and what comes back. * Real-time data intelligence classifies the data in flight, then enforces policy on the spot. That combination is what lets you block an HR manager from seeing SSNs in an AI-generated summary, or redact a confidential field before it reaches the user instead of after the fact. This is the architecture MintMCP has been building at MintMCP, and it is why MintMCP has partnered with Teleskope. MintMCP governs the pipeline through the MCP Gateway: which servers an agent can reach, which tools it can call, and per-user identity on every request. The gateway terminates the connection between the AI client and the data source, so it sees each tool call the way the protocol describes it, which tool, which arguments, and the full response coming back. That position is what makes inline classification possible, because it is the one place with enough structure to read the payload in both directions and act on it. Teleskope classifies the data moving through that pipeline in real time and enforces policy at the point of the tool call, so sensitive fields get blocked or redacted before they ever reach the user. Teleskope published a clear breakdown of how MCP gateways and DLP/DSPM fit together if you want the full architecture. See it on your own data. The fastest way to understand where your agents are exposed is to watch the two layers run against your own sources. Book a demo and MintMCP will walk through how MintMCP and Teleskope close both leak paths in your environment.