Javed Hasan and the Family Business of Asking What’s Inside

Javed Hasan’s startup mentor had a useful qualification: he had already done the thing Hasan was considering. He was also Hasan’s son. After a long career in cybersecurity, the father watched the younger founder build a data startup and found a reason to attempt a company of his own. Silicon Valley likes a story about experience passing from one generation to the next. Here, the advice came back upstream.

“He’s still my number-one advisor,” Hasan has said. It is an unusually revealing detail in a profession whose biographies tend to arrive polished into lists of titles. An executive can know a great deal about products, customers and corporate machinery while still needing someone to ask about the peculiar machinery of starting over. Hasan was willing to ask.

The mentor was already in the family

His account of entrepreneurship includes a piece of counsel from his son: imagine water flowing downhill. When a rock intervenes, go around it without losing the direction of travel. Hasan distilled the lesson into a compact instruction: “Think deeply, pivot rarely, adjust quickly.” The image is pleasingly free of boardroom furniture. There is an obstacle, a destination and a sensible refusal to spend the afternoon arguing with geology.

That advice makes room for two qualities founders sometimes struggle to keep together. You need enough conviction to pursue an idea when it is still difficult to explain. You also need enough flexibility to notice when the immediate route is blocked. In Hasan’s telling, a small adjustment can preserve a larger purpose. Changing everything whenever the terrain becomes inconvenient would defeat the point.

The family connection also gives his decision some scale. His son’s example made the possibility of founding a company tangible. This was someone close enough to observe, and experienced enough to consult. The leap still involved unfamiliar work. Having a person to call did not erase the difficulty; it gave the difficulty somewhere to go.

“Think deeply, pivot rarely, adjust quickly.”

Javed Hasan

A career spent making security usable

Hasan’s education crossed engineering and business. He earned a B.Tech from the Indian Institute of Technology Kanpur, an MSIE from Louisiana State University and an MBA from Georgia State University. His professional biographies place him at Symantec, McAfee, Norton and Trellix. They also describe advisory work with startups including Accurics and TransientX, both subsequently acquired.

At Symantec, his work included the Integrated Cyber Defense Manager, a central cloud console, and the launch of its SaaS endpoint security business. The company’s summit biography credits him with building and scaling more than 50 cybersecurity products over a career of more than three decades. The throughline is product management: turning a technical capability into something another organization can actually deploy, understand and keep using.

There is a particular education in that work. A security product has to make sense to the people buying it and the people operating it. Those are not always the same people, and they do not always ask the same questions. The engineer wants a usable change. The security leader wants an account of the risk. Someone else wants to know why the meeting has generated another meeting.

Hasan’s move into founding brought that experience together with Anand Revashetti, Lineaje’s CTO and co-founder. The two had crossed paths at McAfee. Their new company addressed a question that sits underneath the familiar business of protecting applications: how much does an organization know about the software it has decided to trust?

The ingredients brought their own ingredients

Lineaje’s early product, SBOM360, worked with software bills of materials. An SBOM records an application’s components and dependencies. The deceptively ordinary word is “dependencies.” A developer brings in a useful library; that library relies on other libraries. The finished application carries decisions made elsewhere, sometimes several steps away from the team whose name appears on the finished product.

For a buyer, the visible product and the assembled product can therefore be very different objects. The interface may be tidy while the component history is complicated. Hasan’s concern is the distance between those two views. Software can become indispensable to a business before the business has a sufficiently detailed account of its origins.

In a foreword to Lineaje’s open-source research, he used the Trojan horse as his analogy. More telling than the horse was his instruction about the people pulling it inside: developers should not be blamed for lacking tools to inspect the deeper supply chain. That is a product builder’s response to a security problem. Find the missing capability, then give the people doing the work a way to use it.

The company attracted a $7 million seed round, disclosed in February 2023, followed by a $20 million Series A announced in July 2024. That brought disclosed funding from those rounds to $27 million. The later round included investors such as Prosperity7 Ventures, Neotribe and Hitachi Ventures, alongside Tenable Ventures. Financing supplied resources for the problem; it did not make the underlying dependencies any less tangled.

A Sith Lord with a product roadmap

There is a more playful public version of Hasan. In December 2023, he appeared in dope.security founder Kunal Agarwal’s product-management series under the title “Tips from Sith Lord Javed Hasan.” The accompanying artwork supplied the robes and lightsaber. Product management, apparently, had reached the stage where a roadmap could use a little intergalactic menace.

The lessons underneath the costume were recognizable: care about the work, maintain conviction, communicate that enthusiasm to customers and celebrate progress with the team. The appearance is a welcome interruption to the usual executive vocabulary. A product manager still has to get other people interested enough to act. Even an excellent specification cannot do all the persuading on its own.

Set beside the advice about water and rocks, the episode offers two different ways of talking about persistence. One comes from a family conversation; the other borrows theatrical equipment from a galaxy far away. Both make a technical career easier to picture. Neither requires pretending that Hasan’s work happens without other people.

When confidence outruns the inventory

By April 2026, Hasan was examining a newer version of the visibility problem. In his account of Lineaje’s RSAC survey of enterprise security leaders, 86 percent of respondents’ organizations were using AI-generated code in production, while 17 percent reported full visibility into it. Those figures describe the company’s survey, rather than a census of every enterprise. They nevertheless explain the gap he wanted readers to consider.

There is a human appeal to deploying a tool that makes work move faster. Asking for a complete inventory is a less glamorous request. Hasan’s argument puts those activities back in the same conversation. An organization’s confidence in its defenses has limited practical value if the organization cannot describe what it has deployed.

His September writing pushed the argument further downstream. Finding a vulnerability leaves several consequential questions unanswered. Can someone exploit it in this environment? Can a patch be applied without disrupting the application? What evidence shows that the weakness has been closed? His discussion of Frontier Defense placed the emphasis on tested, verified remediation.

That focus is consistent with the operational demands of a product career. An alert can be accurate and still leave its recipient with a difficult afternoon. A proposed fix can look persuasive and still fail a build. The useful unit of progress becomes a change that survives testing, with enough evidence for someone else to judge it.

The next ingredient can act on its own

The rise of AI agents gives Hasan’s original question another complication. A component can now participate in a workflow, use tools and take actions. Understanding what is installed remains necessary; understanding what it is allowed to do becomes part of the same job. The inventory has acquired verbs.

In May 2026, Hasan described UnifAI as a way to bring governance into the development of agentic applications. His stated aim was to discover AI assets, establish policies and apply controls within the workflow. He wanted organizations to address the rules while building the system, rather than leave every difficult interpretation to a later manual review.

By October, his writing was examining 26 AI threat reports and the ways agents could be steered into unwanted actions. His attention had moved beyond the authenticity of a software package to the instructions and context influencing software behavior. It was an extension of the same professional concern: the organization remains responsible for what it has invited inside.

Hasan’s next chapter will be judged by how well those ambitions translate into working products. The more personal lesson is already available. After decades in an industry, he found room to become a beginner at another part of it, and room to take advice from his son. Experience had brought him to the question. Asking someone else helped him take the next step.