Message-ID: <1945097920.1598.1556112004742.JavaMail.javamailuser@localhost> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1597_1012207001.1556112004741" ------=_Part_1597_1012207001.1556112004741 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Security FAQ

Security FAQ

It's important you make sure the reporters and users of any map = you build understand the risks involved:

Can admin erase IP and any evidence of where messages are coming= in from? (I recognize that in some countries - like the UK - this is illeg= al)

Just had a quick search in the code and can't track down the IP related = bits, so not sure what you can do with those.
However even if you can remove these from Ushahidi, it's important to real= ise these often end up in server logs anyway, so they might be harder to = remove if you don't control the server.

In the case of SMS I note that there are suggestions to delete s= ent messages but in fact if people's phones are monitored or there is press= ure
on the telco or just because of tower pings, wouldn't it be easy to= pinpoint which cellphones sent in information? Is there a secure way to
use sms?

SMS can definitely be tracked by the telco. Obviously it depends on wher= e you're operating as to how likely this is.

How you mitigate this will depend on the situation. In some cou= ntries you can get prepay sim cards without supplying any ID, so while the= phone is traceable to the sim/phone number, its not traceable to the indi= vidual.
With any information you collection it is usually best only to collect the= information you need. If you don't need the name of a reporter, don't col= lect it.

However, in cases of greater security risk, do you have suggesti= ons for secure hosting and if SSL certificates can help or hinder data inpu= tting...
We would recommend always using SSL with a valid certificate, even on a l= ow risk deployment. This reduces (but doesn't eliminate) the risk of the s= ite being hacked and details being monitored.

------=_Part_1597_1012207001.1556112004741--