Hacker News new | ask | show | jobs
by mattbrewsbytes 2150 days ago
If you get more specific about a problem/pain it solves that costs lots of money and headaches then that might be too low.

The use case I'm thinking of is a user in a call center environment that needs to process a customers credit card transaction. PCI compliance level could dictate that card info not sit in rest on that call center network (I haven't worked in that space in a while). They could use your app to securely run a remote browser on a PCI compliant network and do the transaction.

Sometimes this is solved with hardware from vendors so the call center person has a separate device they need to use to process the transaction (basically a terminal on a protected network). Sometimes the call center is an outsourced function that scales up with call volume and more capacity is restricted to the number of people that have the special hardware.

If its possible to replace the hardware with software and be compliant, that removes a lot of operational cost from the business, way more than $12k/year.
1 comments
win66 2150 days ago
That's a good idea. would it be a bad idea to reach out to my email with some names of companies in this space? I just wouldn't know where to start, it send that what you know would be very helpful. cris@dosycorp.com
link
mattbrewsbytes 2149 days ago
You would have to become versed in PCI compliance and the ins/outs of different levels of that to know if your solution is 100% in line with what the latest security guidance is.

Any company that does a lot of CC processing could be a candidate, throw a dart at the Fortune 500 list and you'll likely hit one. Typically those types of companies expect enterprise solutions.

Small businesses might be a better starting point in that space but they won't have deep pockets. This thread [0] gives a perspective of PCI compliance challenge, security scans, etc.

PCI is just one aspect that I thought of where your solution might fit, there are probably other similar information security pain points you could explore.

[0] https://security.stackexchange.com/questions/214513/being-to...

link