[DEPRECATED] Using Web Security Scanner to Find Vulnerabilities in an App Engine Application avaliações
7714 avaliações
Most of the time in the lab (about 95%) is spent waiting for security scanning to be queued and run. This is not a good use of lab time.
Ernest K. · Revisado há over 7 years
Shiyghan N. · Revisado há over 7 years
Shiyghan N. · Revisado há over 7 years
Eelis O. · Revisado há over 7 years
Vinh H. · Revisado há over 7 years
Harsh D. · Revisado há over 7 years
awesome
Abu A. · Revisado há over 7 years
Really good, informative lab.
Masi M. · Revisado há over 7 years
Dmitri L. · Revisado há over 7 years
It's unclear when to end this lab so that the coursera grade shows as complete.
Sathish V. · Revisado há over 7 years
Bear S. · Revisado há over 7 years
Joseph J. · Revisado há over 7 years
Andy H. · Revisado há over 7 years
Andy H. · Revisado há over 7 years
Danny W. · Revisado há over 7 years
Luciano A. · Revisado há over 7 years
Wilberth E. · Revisado há over 7 years
Rémi d. · Revisado há over 7 years
Security scans take 17 minutes, not "a few"
Fred S. · Revisado há over 7 years
The security scanner shows no vulnerabilities found until it completes the scan. This gives some false impressions that the code was secure whereas, it hasn't finished it's scan yet. If it doesn't provide realtime results, it shouldn't say that nothing was found and give the impression that results can be provided in realtime.
Bobby J. · Revisado há over 7 years
No vulnerabilities were found on the first run.
Crispin v. · Revisado há over 7 years
Min L. · Revisado há over 7 years
Sergio M. · Revisado há over 7 years
Gilbert N. · Revisado há over 7 years
5
Syrus S. · Revisado há over 7 years
Não garantimos que as avaliações publicadas sejam de consumidores que compraram ou usaram os produtos. As avaliações não são verificadas pelo Google.