I don't really understand your idea, but I do have a few comments:
1) I'm skeptical that most corporate users know or care much more about the security of the applications they are using than anyone else. They might take more interest in cases where failure on their part may lead to individual criminal liability however.
2) I think it's more likely that most companies purchase desktop apps rather than web apps (where there are equivalent versions available) because they don't "get" web apps and because something installed on their PC would appear to the less technically minded as being more of a tangible purchase.
3) SSL/TLS connections can encrypt data between user and server. Databases on the server can be encrypted to prevent your hosting provider snooping on your data. You can authenticate your browser to a server using mutual SSL authentication (certificates at both ends) in addition to using log in passwords if you are that paranoid.
Would you like to expand on your idea a little? - I don't see what benefit it really provides.
i think the benefit shall be something like this: instead of feeling insecure about your data and having to request information about security from the webapp provider himself, you would have a single endpoint in the hoster, which commits himself explicitly to security. plus, you could be safer to believe that no harm is done with your data.
Comments
I don't really understand your idea, but I do have a few comments:
1) I'm skeptical that most corporate users know or care much more about the security of the applications they are using than anyone else. They might take more interest in cases where failure on their part may lead to individual criminal liability however.
2) I think it's more likely that most companies purchase desktop apps rather than web apps (where there are equivalent versions available) because they don't "get" web apps and because something installed on their PC would appear to the less technically minded as being more of a tangible purchase.
3) SSL/TLS connections can encrypt data between user and server. Databases on the server can be encrypted to prevent your hosting provider snooping on your data. You can authenticate your browser to a server using mutual SSL authentication (certificates at both ends) in addition to using log in passwords if you are that paranoid.
Would you like to expand on your idea a little? - I don't see what benefit it really provides.
i think the benefit shall be something like this: instead of feeling insecure about your data and having to request information about security from the webapp provider himself, you would have a single endpoint in the hoster, which commits himself explicitly to security. plus, you could be safer to believe that no harm is done with your data.