리뷰 Respond and recover from a data breach개

manoj k. · 8개월 전에 리뷰됨

The lab contained outdated and inaccurate instructions.

Bowie R. · 8개월 전에 리뷰됨

Sheetal Sanjay B. · 8개월 전에 리뷰됨

Sheetal Sanjay B. · 8개월 전에 리뷰됨

Federico E. · 8개월 전에 리뷰됨

Sheetal Sanjay B. · 8개월 전에 리뷰됨

Alexandria Y. · 8개월 전에 리뷰됨

Didn't recognise i'd enabled logging possible because i did it from 'wrong' place. And didn't know i was supposed to name the new firewall rule 'limit-rules' until after i'd created one called something else.

Alan M. · 8개월 전에 리뷰됨

Elie P. · 8개월 전에 리뷰됨

Roshan B. · 8개월 전에 리뷰됨

Check description. Many names have changed OR are in different places.

Evelina K. · 8개월 전에 리뷰됨

ARJUN A. · 8개월 전에 리뷰됨

again, followed instructions and had issues with it confirming I did it right. This is the WORST labs you guys have by far

Eric V. · 8개월 전에 리뷰됨

Callanga, A. · 8개월 전에 리뷰됨

Task 5 needed to toogle logs on and off about 3 times to get full credit

David E. · 8개월 전에 리뷰됨

The instructions seem to be for an older interface, had to look around for the task to complete Ex "Safe boot" Challenge: Enable logging was bugged even if logs were visible in logging the activity was not validated.

V1ctor R. · 8개월 전에 리뷰됨

Task 5 is still broken

David E. · 8개월 전에 리뷰됨

CHI HAN T. · 8개월 전에 리뷰됨

Wolf C. · 8개월 전에 리뷰됨

Thuc Nhien N. · 8개월 전에 리뷰됨

herib26 G. · 8개월 전에 리뷰됨

Test your labs prior to production. Task 5 for firewall logging is broken and your support is pedestrian at best.

David E. · 8개월 전에 리뷰됨

for some reason PCI DSS compliance wasn't able to update to the already fixed issues. there was a missing part at the end , but certain fixed issues were not recognized; even when progress was marked off green.

herib26 G. · 8개월 전에 리뷰됨

Your task 5 says logging is turned off when I turned logging on

David E. · 8개월 전에 리뷰됨

Jacob Y. · 8개월 전에 리뷰됨