21–30 of 36 posts
Do you have the statistics for browser usage at enterprise companies? Obviously you don't support everything yet but I imagine the money in info sec is all up enterprise/micro$oft. Curious what comes after the browser extension.
If so, what bits are you sending? Just the top level domain, just FQDN, entire URL, or are you tracking engagement time on websites as well? How long will you maintain, or plan to maintain, the user's browsing history?
Any plans on monetizing the consumer end of this to build a profile of where the users are spending their time?
Does this send the users entire browsing history to Apozy? If so, what bits are you sending? Just the top level domain, just FQDN, entire URL, or are you tracking engagement time on websites as well? How long will you maintain, or plan to maintain, the user's browsing history? Any plans on monetizing the consumer end of this to build a profile of where the users are spending their time?
If you're opted into privacy scoring it sends only the FQDN of the current site to our service. We conduct privacy scoring on the server side because it would slow down the browser otherwise. If you're opted into community protection, CSP violations are sent with the URL. This allows us to detect undiscovered malicious sites and share them back to the community.
Currently we have no plan to share any information to monetize on the consumer end. We make money by enabling businesses to control fine grain permissions on corporate rollouts.
Genius idea. I just installed it! What are some things coming down the pipeline?
Thanks! We're working on device support across the board, improved privacy scoring, and toying with the idea of adding Google's Perspective - https://www.perspectiveapi.com .
Earlier quoted context omitted.
Thanks! We're working on device support across the board, improved privacy scoring, and toying with the idea of adding Google's Perspective - https://www.perspectiveapi.com .
Apple Safari support in the future? Also, if I'm using a self-updating malware blocklist within extensions such as Ablock Plus, how would Apozy do better than that to prevent phishing?
The reason why we're better at that than an AdBlock is because we use a whitelist approach. When using a whitelist, all the newest sites and attacks are blocked by default. AdBlock will always be slightly behind on that. Additionally, AdBlock won't protect you from inputting your credentials into a phishing site if you somehow end up on a bad site. As a side benefit, since we don't scan the DOM, we don't slow anything down!
Does this send the users entire browsing history to Apozy? If so, what bits are you sending? Just the top level domain, just FQDN, entire URL, or are you tracking engagement time on websites as well? How long will you maintain, or plan to maintain, the user's browsing history? Any plans on monetizing the consumer end of this to build a profile of where the users are spending their time?
There is no data collection by default. Everything is opt-in. The only information we communicate is what you opt into. The browser history stays in your browser and is not sent to Apozy. If you're opted into privacy scoring it sends only the FQDN of the current site to our service. We conduct privacy scoring on the server side because it would slow down the browser otherwise. If you're opted into community protectio…
Maybe I'm not getting how this works, but how can a service like this function without sending the URL (or FQDN etc) to a remote service? It's too much data to have the entire map of all servers on the internet bundled locally (probably a pain to update too...). That said, what does it mean to use this plugin but not opt-in? Is that possible, or are you referring to users opt-in as part of the install?
Earlier quoted context omitted.
There is no data collection by default. Everything is opt-in. The only information we communicate is what you opt into. The browser history stays in your browser and is not sent to Apozy. If you're opted into privacy scoring it sends only the FQDN of the current site to our service. We conduct privacy scoring on the server side because it would slow down the browser otherwise. If you're opted into community protectio…
> There is no data collection by default. Everything is opt-in. The only information we communicate is what you opt into. The browser history stays in your browser and is not sent to Apozy. Maybe I'm not getting how this works, but how can a service like this function without sending the URL (or FQDN etc) to a remote service? It's too much data to have the entire map of all servers on the internet bundled locally (pr…
Using the extension without opting in means you don't see site privacy grades but you're still protected using a Trust on First Use model of security created with your browsing history.
Earlier quoted context omitted.
> There is no data collection by default. Everything is opt-in. The only information we communicate is what you opt into. The browser history stays in your browser and is not sent to Apozy. Maybe I'm not getting how this works, but how can a service like this function without sending the URL (or FQDN etc) to a remote service? It's too much data to have the entire map of all servers on the internet bundled locally (pr…
We don't need to send any information to our service to protect you from bad sites because that is handled locally. The browser history already exists so the load on your machine is the same with or without Apozy. We use the headers to make it efficient for a large number of sites - 1M+ Using the extension without opting in means you don't see site privacy grades but you're still protected using a Trust on First Use…
Okay so the local version is comparing the user's current page vs. the sites they've gone to prior? And if it seems off based on some heuristics it flags the page. Interesting idea.
Wouldn't work for me though as I have my browser set to nuke everything each time it's closed.
> Using the extension without opting in means you don't see site privacy grades but you're still protected using a Trust on First Use model of security created with your browsing history.
I originally thought it was just this piece which would need some type of client / server interaction to either fetch the "bad lists" or send the current URL/FQDN for validation.
Earlier quoted context omitted.
We don't need to send any information to our service to protect you from bad sites because that is handled locally. The browser history already exists so the load on your machine is the same with or without Apozy. We use the headers to make it efficient for a large number of sites - 1M+ Using the extension without opting in means you don't see site privacy grades but you're still protected using a Trust on First Use…
> We don't need to send any information to our service to protect you from bad sites because that is handled locally. The browser history already exists so the load on your machine is the same with or without Apozy. We use the headers to make it efficient for a large number of sites - 1M+ Okay so the local version is comparing the user's current page vs. the sites they've gone to prior? And if it seems off based on s…
If you don't nuke your local storage, it should still work. I do suspect it may be more annoying without any browser history to go on because there's no model built, so you have to 'prime the pump' a little more than a user who has history would have to.
-Erhan
Earlier quoted context omitted.
> We don't need to send any information to our service to protect you from bad sites because that is handled locally. The browser history already exists so the load on your machine is the same with or without Apozy. We use the headers to make it efficient for a large number of sites - 1M+ Okay so the local version is comparing the user's current page vs. the sites they've gone to prior? And if it seems off based on s…
> Wouldn't work for me though as I have my browser set to nuke everything each time it's closed. If you don't nuke your local storage, it should still work. I do suspect it may be more annoying without any browser history to go on because there's no model built, so you have to 'prime the pump' a little more than a user who has history would have to. -Erhan