I get comfort from all the efforts that 4D has made to be very secure, but when a customer hands you a 644 cyber security audit report and says “Address these issues”, I need to know where to begin.
It’s one thing for 4D to be able to say their product can pass all security audits, but there seem to be myriad ways for a developer to compromise that security by not following best practices. Most 4D developers are not cyber security experts, so we rely on best practices to guide us. Is there a concise comprehensive guide to best practices for 4D development with respect to Web Security? If not, I think this would be a great Tech Note/Summit Session. Tom Benedict > Lutz, > > Perfect, this is the information I was looking for. > > In the Apache example, when you say you are running multiple instances of > your application, are you manually implementing the load balancing or somehow > have Apache performing the load balancing? > > This load balancing is something of great interest to me, especially when > wanting to run multiple instances, but it is an area I'm not very strong in. > Are you using 4D Client as the "instances" all pointing to a single 4D Server? > > Any insight is appreciated! > > Best, > > Steve ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
