Tag Info

New answers tagged

0

The biggest thing you want to do is to understand and then communicate what your expectations are. If your security model forbids opening a firewall port, is that documented? (As an aside, if you expect that you're safe because you're behind a firewall, I suggest rethinking, but I think you're using that as an example.) You can either document in a ...


1

Typically, your code would be tested & remediated against vulnerabilities in pre-prod/staging environments before going in to production. Yes, not all environments are same so some measures I've taken are using Splunk (aka log correlation tools) to monitor deployments and correlating it with web activities for {x} hours after the deployment. This ...


2

Typically what you would do here is integrate some form of testing procedure into your deployment or post-deployment process. This could be as lightweight as a simple port scan, which could identify ports left open inadvertently, or as large as a full 3rd party security assessment (aka penetration test) where you contract a 3rd party to review the security ...


1

Real penetration testers should not be using their own office bandwidth. If you attempt to access a system from a registered IP address, it's not that difficult to reverse look-up to be able to see where the traffic is coming from. If this is a red team / blue team scenario, then the internal staff already know who the attacker is, and may adjust their ...


0

In most cases the company that is performing a penetration test for a client faces little risk. If the client is actively compromised by some nasty attackers, or really nasty malware - it is possible that threat may make its way into the service provider's (Company "A") machines while the test is being conducted. In addition one would at least hope that ...



Top 50 recent answers are included