views:

269

answers:

1

Silly question: Does Apple provide specific guidelines for contacting servers via http vs https? Also, what data is considered to require https (ie password, geopoint, bank data, etc.) Is there a concrete guideline from Apple on this? More specifically, does anyone know exactly how Apple checks/verifies that an application should or should not be "pulled" from the appstore? Does this even exist or is it a secret?

My manager is worried about not getting approved unless we do everything via https. I think this is a big mistake. Our application basically deals with timesheet and expense data for employees (ie I drove this number of miles, worked on this project for 2 hours, etc.) Because, subsequent to logging in, there are no passwords, geopoint locations, etc., I feel that https for authentication only would be ideal for obvious performance reasons. But perhaps there's are specific guidelines from Apple? Search on http://developer.apple.com, but didn't find, help/links would be appreciated. Thanks all.

+2  A: 

One answer to your question is that Apple wrote this Secure Coding Guide, containing the following paragraph:

No network should be considered to be secure without the use of a secure networking protocol. Even if you are using an internal network with no connections to the Internet, you need to use secure communication protocols and encryption to protect critical data. In a 2005 security survey by CSO magazine (in cooperation with the U.S. Secret Service and Carnegie Mellon University Software Engineering Institute's CERT Coordination Center), 23% of respondents said current or former employees were the greatest cyber security threat. Because 21% of the companies surveyed weren't sure who was the greatest threat, the real number may be higher. Software to intercept network communication packets is readily available. It's not paranoia to think that one of your employees might be trying to steal secrets over your internal network.

but please consider the following. The question should not be "what is the blanket recommendation", but then nor should it be "what does my boss want". The questions should be - what risk is there in allowing the data to travel unencrypted, what risk or cost is incurred in mitigating that risk, and where does the balance between those two lie? What risk/cost is the company willing to accept?

Graham Lee
Ha, I'm reading that guideline right now ;) So far, a lot on Buffer Overflows, etc.
Rob
I'd linked specifically to the paragraph about network transport encryption! I've now quoted it.
Graham Lee