Tag Info

Hot answers tagged

17

Your carrier certainly sees the target IP address of the packets that you are asking them to transmit. The carrier's job is to, indeed, carry your packets from your phone to the base station, and, from that base station, to route it to the nearest infrastructure link so that it may reach its ultimate destination. In your case, all the packets that you send ...


4

Your carrier would not see your VPN address directly, because that is in the encrypted part of the VPN traffic -- all that is visible to them is the public IP address of the VPN endpoint you are connected to. What is most likely happening here is that an app installed by your provider contacted them through the VPN, at which point they can see the address ...


2

Your VPN has an end-point, where the pipe terminates. Your service provider sees this end point, and by using GEO-IP can quickly identify the country, City and even area where this end-point is located. Not sure why you should be surprised about this - A VPN will only protect your communications from YOUR ISP.... Where the traffic appears it will be subject ...


2

So the linked question How is Chase Mobile Deposit Secure? does answer this, just not explicitly. The important thing to remember for this specific scenario is that there is nothing magical about the piece of paper you're thinking of when you picture a check. Just because you get a nice little pre-printed pad of checks from your bank doesn't mean that ...


2

Suppose I write you a check and you deposit it, but also produce a forgery that you deposit a few days later. Soon or late, when I reconcile my account, the forgery will be detected, I'll complain to my bank, and my bank will claw back the money from your account at Chase. Doesn't matter whether it's paper or a picture. If the forgery happens to overdraw ...


2

If you're sure you never store the payment details, not even in things like swap files or core dumps, then I think SAQ-C will be sufficient. I think it's almost certain that you'll need to change some of your processes to complete the SAQ successfully; you won't just be able to fill it in and say that you're done.


1

Thieves are stealing phones now, not for the value of the phone, but because before it's reported lost or stolen they're dialling premium rate numbers which they control. They get a share of the revenue from dialling the numbers so they steal the phone, transfer the SIM to another phone and then call the premium rate number. The original owner of the phone ...


1

I think that question have the answer: they don't have to verify more than they already do. Check routing numbers are all that they need, and they do it for a long time. You forgot that they know your name, address, SSN and a lot about you. Yes, you can pass a counterfeit check once, but they WILL know it sooner or later, and they will Chase you. They will ...


1

The mobile application cannot currently be validated or considered a compliant payment application. Guidance on security and compliance in mobile applications has been issued by the SSC here: https://www.pcisecuritystandards.org/documents/Mobile_Payment_Security_Guidelines_Merchants_v1.pdf As your environment is receiving and transmitting cardholder data, ...


1

I agree with Mike Scott that SAQ-C should be ample in your case. SAQ-C does require you to be scanned by an ASV. Do mind that you don't store any cardholder data at any point. It's important to verify that you: clear logs prevent crashdumps containing cardholder data For mobile applications you should ensure to use non-serializable datatypes. This ...



Only top voted, non community-wiki answers of a minimum length are eligible