What is your primary use case for iboss?

iboss is primarily used for cloud security, helping to protect users when they access websites and cloud applications through secure web access, web filtering, and protection against online threats. In my day-to-day work, I use iboss cloud security tools to monitor and troubleshoot user access issues. For example, if a user cannot access a website or cloud application, I check the security policy, user traffic, and logs to identify the issue. I verify whether the traffic is blocked by a security policy or affected by a connectivity issue. After identifying the root cause, I take the required action and update the incident tickets. The main goal of using iboss is to provide secure access to web applications and protect users from online threats. It helps enforce security policies, monitor web traffic, and troubleshoot access issues, which improves security and helps users access applications safely.

iboss is primarily used for content filtering within school districts and public K-12 school districts, and it can also be used as a firewall for antivirus, anti-spam, and related security functions. In my workflow, iboss fits well because a recent school district had used prior firewalls including Fortinet, Barracuda, and SonicWall before settling on iboss as their primary firewall. The students were always protected, and the content filtering worked very well, seeming to work better than other products we had tried previously. iboss protected approximately 2,000 students and 400 teachers. Regarding my main use case for iboss, I really appreciate that it has a modular option, allowing you to purchase what you need for a specific situation. Because I work with not only educational clients but also small and medium business clients who may not need the content filtering as much, the modular approach gives me the option to provide that functionality and explain how iboss operates as a modular system.

I use iboss as a cloud-based secure web gateway to provide secure internet access, web filtering, and protect remote users from web-based threats. In my day-to-day work, I enforce web access policies for remote users, block malicious websites, and monitor internet traffic to reduce phishing and malware risks. I was able to remove separate on-premises web filtering and proxy solutions, along with VPN-based internet access for remote users, by consolidating into iboss's single pane of glass. After implementing iboss, I consolidated secure web gateway, web filtering, and remote user security into a single, cloud-managed platform which reduced the need to manage multiple tools, simplified policy administration, improved visibility across users and devices, and lowered operational overhead. It also made it much easier to secure hybrid and remote work environments from a single console. Consolidating management into iboss's single pane of glass has helped my organization reduce operational costs by around twenty to twenty-five percent. I no longer needed to maintain multiple legacy web security tools or spend as much time switching between different management consoles, which reduced administrative effort, simplified policy management, and improved troubleshooting, allowing my security team to focus more on threat detection and incident response rather than routine management tasks. The single pane of glass console has significantly helped my organization improve security, resulting in an estimated fifteen to twenty-five percent reduction in overall security management costs. I assess iboss's visibility into cloud, web, and private applications as exceptionally strong and comprehensive because it provides my security team with complete real-time telemetry across all user traffic, regardless of device location or network environment.

We used iBoss mainly for Internet Access by having an Agent on Windows laptops Primarily because when we try to use it on Mac systems, it does not work as expected. On the Windows system, around 45,000 to 50,000 systems, we installed the iBoss agent, and we use that for internet purposes. From an end-user perspective, they do not see any major difference or a major problem with iboss. The agent automatically connects to the cloud, and they do not see much difference. However, when you have any applications, sometimes what happens is that application does not follow iboss settings, and it will not go to the internet. That is where they need to manually set those proxy variables in their application. Otherwise, it is a silent application that works silently, sends you a pac file onto your browsers, and then routes to iboss related data centers, and from there you go to the internet. From an end-user perspective, it is very easy. However, when you implement it, you need to be careful because if you make any mistake and lose that connectivity, then it is a problem to revert on every end-user system. For cloud, web, and private applications visibility, iboss has performed well regarding private applications, particularly with ZTNA related connectors. We have not used them extensively, but the testing we did was auspicious. They can provide connections and potentially replace Cisco AnyConnect in terms of VPN services. The single agent can provide private connectivity to on-premises networks or your data centers and offer internet access. However, we lack practical experience as we did not utilize these features while engaging with iboss.

I use iboss for corporate VPN and all the corporate VRF, with basically all user traffic proxying to the internet.

Previously when I used iboss, we did the POC for iboss for ExxonMobil. Four or five people wanted to move from our old proxies to cloud proxies, and we did POCs with different giants at that time. What we were looking for was proper categorization and nodes that would have global reach. We were also looking for latency specifics to determine how the latency could be better with the on-prem devices compared to cloud devices. We also implemented VPN zero trust, which was another requirement, and that structure is what we decided to go with.

We use it primarily for simpler filtering because we're a K12 entity.

We used it for student and faculty filtering on campus.

We are a PreK-12 public school district, and we use iboss to filter internet content for our students at home and staff member devices to ensure they do not access inappropriate sites.

We use iboss for cloud proxy, CASB, and SSL inspection. I am gradually evaluating the zero trust feature of it.

We use it for URL filtering to enforce our enterprise Internet use policy. We use it for our current initiatives in artificial intelligence. There's a module in iboss for artificial intelligence we're utilizing. We use it for forensics when our internal affairs investigators need historical information on website access. We use their cloud configuration to send our enterprise-owned devices anywhere in the world, and we've enabled the protections to travel with the end user. We also have some botnet and malware and other protections through that agent, and we are currently evaluating the iboss platform to see if their zero trust framework and legacy VPN solution will work in our environment. We've been fanning out. Iboss started out with us as just a simple URL filter, and it has moved on to be used in several key critical areas of our operation.

We purchased iboss for its SASE and ZTNA features. We're currently utilizing the SASE capabilities and have plans to deploy the ZTNA functionality in the future. We're also using the web browser sandboxing feature for some limited use cases. We currently have approximately 80,000 users on the platform. iboss is primarily a cloud-based solution, but I tend to think of it more as a platform-as-a-service due to its deployment flexibility. In its most basic form, it utilizes distributed points of presence globally, and agents on our devices connect to the nearest one for seamless backend routing. However, for data center needs, they offer physical hardware for on-premises installation, bridging those environments into their network. They have similar solutions for cloud integration as well. So, while fundamentally a cloud service, iboss's adaptability has allowed us to address all our advanced deployment requirements.

We use iboss for the proxy solution. I used iboss in my organization to block a few sites for a few of my employees.

We use the solution for web filtering to secure networks from malicious websites.

The solution is a corporate proxy server, an intelligence proxy.

My role is security solutions architect. I do the research for the customers. We are implementors and consultants. We provide solutions for our clients. With everybody working from home due to COVID, iboss was the solution that we implemented as the security architecture for those who were working from home and normally don't. It has decentralized the office.

Our primary use case for this product is DLP, data loss protection for databases. We also have solutions for patch management from Ivanti.