Qualys Technical Series - Scanning Best Practices

แชร์
ฝัง
  • เผยแพร่เมื่อ 14 ต.ค. 2024
  • Are you sure you're scanning all of your assets? Join the Technical Series with a Qualys Security Solution Architect to learn how vulnerability scans work and how to get the most out of them for your environment.
    This session will cover:
    The anatomy of a Vulnerability Scan - The scan process (host discovery, port discovery, service discovery, vulnerability scan) and option profiles.
    How to set up, use and troubleshoot Authentication Records.
    Scanning strategies - Light Inventory vs Map, full-range vs targeted scanning, scanning cloud agent assets.
    Scanning best practices - Firewalls, the natural enemy of vulnerability scanning, VLAN trunking, seamless scaling for scanner appliances.

ความคิดเห็น • 5

  • @TeshornMakingMoves
    @TeshornMakingMoves ปีที่แล้ว +2

    Learning from your videos. Thanks.

  • @olympushasfallen8265
    @olympushasfallen8265 3 ปีที่แล้ว +1

    What does Qualys recommend as far as vulnerability scanning: use of a scanner appliance or cloud agents? Do cloud agents perform authenticated scanning on default?

    • @aculeus1971
      @aculeus1971 2 ปีที่แล้ว +1

      Cloud Agents are recommended as they are authenticated and will upload metadata about changes by default, every 4 hours. While it is possible to scan every day using the Qualys scanner, a number of organisations find this challenging and might manage 1 scan per week or per month ...

    • @Andy-bi9bl
      @Andy-bi9bl ปีที่แล้ว

      @@aculeus1971 I know I am late to the party, however why do you see those scanns challenging? Is it because of the cost or it is time-consuming/resource-consuming?

  • @manikandanmohan9216
    @manikandanmohan9216 2 ปีที่แล้ว

    We have 50 servers in our environment, While install qualys agent through azure extension the agent installed in 40 servers without any issues, but remaining 10 servers got failed. Kindly let me know where should I focus about the issue. Error: Scanner to timeout failure