In December 2024, Gil Shwed opened his calendar and removed the meetings. Roughly fifty a week disappeared. After three decades running Check Point, the cybersecurity company he had founded with two friends, he had become executive chairman. There was a new CEO. There was suddenly room to think. There was also the rather unfamiliar question of what, exactly, he would do next week.
He described the adjustment a few months later with a programmer’s specificity. He still went to the office every day. He now had one or two meetings a day instead of ten or twelve. The change was large enough to require learning. For someone whose working life had been organized around the same company since 1993, freedom arrived as a scheduling problem.
It is a useful place to begin with Shwed. His public story contains the usual furniture of a technology fortune: the early talent, the borrowed workspace, the Nasdaq listing. The more interesting question is how a person remains curious about one problem for thirty years, then makes enough room for someone else to have a go at it.
The boy who kept knocking
In Jerusalem, long before Check Point, computers were an activity Shwed chose for himself. His father was a systems analyst working with IBM mainframes. As a child, Shwed took an hour-long bus ride across the city for a computing class at a religious community center. He would arrive before it opened and wait. A hobby with that commute had already become something more serious.
By twelve he had a summer programming job, working at a company involved in automated translation. At fourteen he wanted to study at the Hebrew University of Jerusalem. The university had an objection: he was fourteen. In his later recollection, he spent six months returning to ask whether a decision had been made. Eventually, with the semester beginning and the committee still undecided, he was allowed to attend classes.
That episode has the pleasing shape of an early Shwed product demonstration. An institution presents a boundary. He keeps examining it until a workable passage appears. He studied computing while still at school, but entered military service without completing a degree. The honorary doctorates would come later, after he had supplied universities with a rather different reason to admit him.
A wall that remembered the conversation
During his service in Unit 8200, Shwed worked on a problem that sounds simple until the consequences become apparent: connect networks while keeping sensitive information contained. A cable can make two systems neighbors. It cannot decide what neighbors should be allowed to know about each other. That requires rules, and software capable of applying them.
Shwed’s contribution to commercial network security was stateful inspection. A stateful firewall remembers active connections and uses that context when evaluating the traffic passing through it. An incoming packet belongs to a conversation, or attempts to start one. Remembering the conversation gives the firewall more to work with than an isolated address and a port number.
A simplified view of stateful inspection, the technology behind Check Point’s early firewall.
The distinction matters to his biography. Firewalls existed before Check Point. Shwed helped develop and commercialize an approach that made them practical for a growing market. Giving him every invention in the vicinity would obscure the achievement that actually mattered: turning a difficult security problem into a product organizations could buy and use.
He did not immediately start a company around the idea. After military service he worked as a software developer at Optrotech, where he met Marius Nacht. Shlomo Kramer was a friend from his military days. When commercial use of the internet began opening up, the technology acquired a much more inviting purpose. Businesses wanted to connect. They also wanted some control over who could come back through the connection.
Grandmother’s apartment, global ambitions
In 1993, Shwed, Nacht and Kramer founded Check Point. Their workspace was Kramer’s grandmother’s apartment in Ramat Gan. They began in a small room and moved into the living room as the weather and their computers made the place warmer. Technology companies enjoy a garage story. These founders had a domestic variation, with much the same ventilation problem.
The enterprise required more than software. A product made in Israel had to reach buyers elsewhere, so distribution became part of the design. Check Point built its business through resellers. A local partner could introduce a customer to software made by people thousands of miles away. It was a commercial answer to the same geographical problem the internet was solving for programmers.
The early product, FireWall-1, reached the market in 1994. By June 1996, Check Point was listed on Nasdaq. Those dates can make the ascent look automatic. They compress the work of persuading customers that connecting to the internet was worth doing, then persuading them to pay for protection. Shwed was selling a way to participate in a change whose scale was still being argued about.
By 2002, a magazine photographer asking Shwed to face the camera encountered an unexpected bit of stage direction. He preferred a profile, gazing into the distance, because, he joked, “it makes me look visionary.” For an executive routinely described as quiet, it was a nicely timed puncture of the technology portrait. Apparently even foresight benefits from knowing your angle.
The boss was in the kitchen
People who worked with Shwed described an analytical listener. Ray Rothrock, an investor and Check Point board member, recalled someone who collected information, reached his own conclusions and did not need to dominate a conversation. The picture is of a manager interested in understanding the machinery, including the human parts, before announcing what should happen next.
Rothrock also described management meetings at Shwed’s home, where the founder cooked multicourse meals for managers visiting from branch offices around the world. The detail improves an otherwise dry executive biography considerably. An international management structure is easier to picture when someone has to finish preparing dinner. It also gives the quiet host a fairly practical way to bring a room together.
His attachment to the company did not require him to explain everything through his own background. In a 2002 interview, he emphasized the similarities among colleagues of different nationalities. Check Point was a technology business with people around the world. Israel was its starting point; the work depended on being useful well beyond it.
That outlook helps explain the longevity. A security vendor’s customers are buying continued usefulness. Every new way of working, from remote access to cloud applications, changes the job. A founder can keep returning to an original question while discovering that the practical answer needs another revision.
Success is an attack that never happened
Across the years, Shwed returned to prevention. Finding out that information has been stolen can help explain an incident, but it cannot make the information private again. He argued that security should stop an attack before the damage occurs. There is a stubborn common sense to the position. A beautifully formatted account of a burglary is limited consolation for the missing silver.
His product thinking also moved toward bringing protections together. A threat arriving through email should not escape attention simply because the next stage involves a different application or device. He wanted systems to share what they knew and administrators to manage fewer disconnected pieces. The ambition extended the early firewall’s promise: make useful connections possible without asking the user to become a security specialist.
Scale brought its own awkwardness. In 2023, he discussed the difficulty of keeping a large engineering organization dependable while allowing smaller groups to move quickly. Check Point called some of those more independent efforts “rockets.” A founder who once worked in an apartment was now trying to preserve some of a small team’s speed inside the institution that apartment had produced.
The size of that institution was visible when Check Point reported 2024 revenue of approximately $2.56 billion. Revenue had grown six percent over the preceding year. Such figures describe a business with customers, obligations and routines that continue beyond the founder’s daily instructions. Building it had taken decades. Allowing it to operate under a successor required a different kind of confidence.
A successor with a different temperament
Nadav Zafrir became CEO on December 16, 2024, as Shwed moved into the executive chairman’s role. Zafrir had co-founded Team8 and worked across the cybersecurity industry. Shwed had known him for years. The appointment followed a search that examined candidates internationally, rather than an assumption that the next leader should simply resemble the last.
Chairmanship still came with work. The company set out responsibilities including mentoring the CEO and senior executives, supporting technology and research, and helping guide long-term strategy. Shwed remained involved while the operating authority moved. The arrangement gave the founder a place to contribute without requiring the company to organize every decision around his previous job.
By June 2025, he was willing to entertain a less flattering interpretation of the timing: perhaps he should have stepped aside earlier. He said earlier internal candidates might have led the company, too. It was an unusually useful admission from someone entitled to spend an interview polishing the record. Achievement did not make every choice retrospectively correct.
“My wish is for Check Point to always stay independent.”
Gil Shwed, February 2025
Independence remained an explicit ambition. So did making room for change. His other commitments, including youth education and the Yeholot Association’s work to reduce school dropout rates, gave that idea a life outside the company. When he received the Israel Prize in 2018, he shared the credit with Kramer, Nacht and Check Point’s employees; the associated prize money was designated for charity.
The empty calendar was never likely to stay empty. But for Shwed, it represented something he could not have obtained by adding another meeting. After years spent deciding which connections to permit, he had opened a little space of his own. The next question was worth giving it time.