컬렉션을 사용해 정리하기
내 환경설정을 기준으로 콘텐츠를 저장하고 분류하세요.
멀웨어 감염 방지
멀웨어를 방지하려면 끊임없이 감시해야 합니다. 이 문서에는 멀웨어 감염을 방지하기 위한 도움말이 포함되어 있습니다. 그러나 최신 정보가 누락되었을 수 있으므로 웹사이트 소유자는 이를 더욱 철저히 조사하는 것이 좋습니다.
사이트 상태 모니터링
Search Console의 다양한 기능을 사용하면 잠재적인 문제를 식별할 수 있습니다. 예는 아래와 같습니다.
-
Google이 내 사이트에서 찾은 페이지를 확인하려면
site:
검색 연산자를 Google에 검색해 보세요. 주기적으로 이 작업을 실행하여 누군가가 내 사이트에 예상치 못한 페이지나 콘텐츠를 몰래 삽입하지 않는지 확인하는 것이 좋습니다. 사이트에 알 수 없는 페이지나 내가 작성하지 않은 주제가 표시되면 해킹을 당한 것일 수 있습니다. site:
검색 연산자는 특정 사이트로 검색을 제한하기 위한 방법입니다. 예를 들어 site:developers.google.com
을 검색하면 Google Developers 사이트의 결과만 반환합니다.
- 보안 문제 보고서에는 Google이 사이트에서 파악한 해킹된 페이지와 함께 문제 해결 방법에 관한 안내가 표시됩니다.
-
Google이 사이트에서 멀웨어를 감지하면 Search Console의 메시지 패널에 알림이 표시됩니다. 메시지가 이메일 계정으로 전달되도록 하면 이러한 알림을 신속하게 받을 수 있습니다.
보안 점검 사항
사이트를 정기적으로 모니터링하는 것 이외에 다음을 실행하는 것이 좋습니다.
모든 웹사이트 소유자
-
안전한 비밀번호를 선택합니다.
Google 계정 가이드라인을 참고하면 도움이 됩니다.
-
타사 콘텐츠 제공업체는 신중하게 선택합니다.
사이트의 타사 앱 및 광고 소스가 정상적이고 신뢰할 수 있는지 확인합니다. 정상적이고 신뢰할 수 있는 소스는 웹사이트에서 지원 및 연락처 정보를 제공합니다.
-
호스팅 회사나 게시 플랫폼에 지원을 요청합니다.
대부분의 회사에는 유용하고 대응력이 뛰어난 지원 그룹 또는 보안 페이지가 있습니다. 보안 페이지나 사이트에 RSS 피드가 있으면 이를 구독하여 최신 정보를 받아 보세요.
-
모든 컴퓨터를 안전한 상태로 유지합니다. 특히, 웹사이트에서 작업할 때 로컬 워크스테이션에 최신 소프트웨어가 있는지, 바이러스나 트로이 목마 또는 유사 멀웨어로부터 안전한지, 설치된 바이러스 백신 소프트웨어가 최근에 업데이트되었는지 등을 확인하시기 바랍니다.
서버 액세스 권한이 있는 웹사이트 소유자
If you're a Search Console user and are having trouble with persistent or unfixable security issues on your site, you can let us know.
Report a security issue
달리 명시되지 않는 한 이 페이지의 콘텐츠에는 Creative Commons Attribution 4.0 라이선스에 따라 라이선스가 부여되며, 코드 샘플에는 Apache 2.0 라이선스에 따라 라이선스가 부여됩니다. 자세한 내용은 Google Developers 사이트 정책을 참조하세요. 자바는 Oracle 및/또는 Oracle 계열사의 등록 상표입니다.
최종 업데이트: 2025-08-04(UTC)
[null,null,["최종 업데이트: 2025-08-04(UTC)"],[[["\u003cp\u003eThis guide offers essential tips and best practices for preventing malware infection on your website.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Search Console provides valuable tools, such as the Security Issues report, for monitoring your site's health and identifying potential problems.\u003c/p\u003e\n"],["\u003cp\u003eImplementing strong security measures like choosing robust passwords, carefully selecting third-party content, and regularly updating software is crucial for website owners.\u003c/p\u003e\n"],["\u003cp\u003eFor website owners with server access, securing server configurations, monitoring log files, and staying informed about the latest security updates are vital steps in safeguarding your site.\u003c/p\u003e\n"],["\u003cp\u003eIf you encounter persistent security issues despite implementing these recommendations, Google provides a channel to report them.\u003c/p\u003e\n"]]],["To prevent malware, website owners should monitor site health using Search Console features like the `site:` operator and Security Issues report. Key actions include choosing strong passwords, carefully vetting third-party content, and contacting hosting support. For those with server access, regular software updates, server configuration checks, log file monitoring, and vulnerability checks are crucial. Utilizing secure protocols like SSH/SFTP and staying informed on the latest security news are also recommended.\n"],null,["# How To Prevent Malware Infection | Google Search Central\n\nPreventing malware infection\n============================\n\n\nThe price of freedom from malware is eternal vigilance. This article contains tips and\npointers for preventing malware infection. However, it is by no means exhaustive, and Google\nencourages website owners to conduct more thorough research as well.\n\nMonitoring your site health\n---------------------------\n\n\nMany of the features of Search Console can help you identify potential problems. For example:\n\n- Try a search on Google with the [`site:` search operator](https://support.google.com/websearch/answer/2466433) to see what pages Google has found on your site. It's always a good idea to do this periodically to see whether anyone has snuck unexpected pages or content on your site. If you see unknown pages on your site, or topics that you didn't write, you may have been hacked. If you're not already familiar with the `site:` search operator, it's a way for you to restrict your search to a specific site. For example, the search [`site:developers.google.com`](https://www.google.com/search?q=site%3Asite:developers.google.com) will return results only from the Google Developers site.\n- The [Security Issues report](https://support.google.com/webmasters/answer/9044101) shows any hacked pages that Google has identified on your site, and instructions on how to fix the problem.\n- If Google detects malware on your site, you'll see a notification in the [message panel in\n Search Console](https://support.google.com/webmasters/answer/9388335). To ensure that you're notified quickly, you can have your messages [forwarded to your email account](https://support.google.com/webmasters/answer/140528).\n\nSecurity checklist\n------------------\n\nIn addition to monitoring your site regularly, we also recommend the following:\n\n### All website owners\n\n- **Choose good passwords.** The [Google account guidelines](https://support.google.com/accounts/answer/32040) are helpful.\n- **Pick third-party content providers very carefully.** Make sure that third-party apps and ads on your site are from trusted and legitimate sources. A trusted and legitimate source provides support and contact information on their website.\n- **Contact your hosting company or publishing platform for support.** Most companies have helpful and responsive support groups and/or security pages. If a security page or site has an RSS feed, subscribe to it to make sure you stay up to date.\n- Keep all of your computers safe. Especially when working on a website, make sure that your local workstation has up-to-date software, is clean from viruses, trojans, or similar malware and has recently updated anti-virus software installed.\n\n### Website owners with server access\n\n- **Check your server configuration.** Apache has some [security configuration tips](https://httpd.apache.org/docs/2.4/misc/security_tips.html) on their site and Microsoft has some [tech center resources for IIS](https://www.google.com/search?q=microsoft+iis+security+best+practices) on theirs. Some of these tips include information on directory permissions, server-side includes, authentication, and encryption.\n- **Make a backup copy of your `.htaccess` file** (or other access control mechanisms depending on your website platform). Use your backup file to recover if the following fails. Be sure to delete the backup file once you are finished.\n- **Stay up-to-date with the latest software updates and patches.** There are lots of tools that make building a website easy, but each one adds some risk of being exploited. A common pitfall for many website owners is to install a forum or blog on their website and then forget about it. Much like taking your car in for a tune-up, it's important to make sure you have all the latest updates for any software program you have installed. Make a list of all the software and plug-ins used for your website, and keep track of the version numbers and updates. Even if you're diligent and keep all your website components updated, you may still be vulnerable if your web hoster has not installed the most recent operating system patches. This problem affects not only small sites; there have been warnings on the websites of banks, sports teams, and corporate and government websites.\n- **Keep an eye on your log files.** Making this a habit has many great benefits, one of which is added security. For example, unfamiliar URL parameters (like `=http:` or `=//`) or spikes in traffic to redirect URLs on your site may indicate that a hacker is exploiting [open redirects](/search/docs/advanced/guidelines/sneaky-redirects). Also, bear in mind that hackers often try to alter log files. Take measures to protect these files from attack. For example, you can move these files from their default location, making it harder for hackers to find them.\n- **Check your site for common vulnerabilities.** Avoid having directories with open permissions. This is like leaving the front door to your home wide open.\n\n\n Also check for any\n [XSS](https://www.owasp.org/index.php/Cross_Site_Scripting)\n (cross-site scripting) and\n [SQL injection](https://owasp.org/www-community/attacks/SQL_Injection) vulnerabilities.\n- **Use secure protocols.** Google recommends using SSH and SFTP for data transfer, rather than plain text protocols such as telnet or FTP. SSH and SFTP use encryption and are much safer.\n- **Keep up to date on the latest security news.** The [Google Security Blog](https://security.googleblog.com/) provides useful information about online security and safety, as well as pointers to other resources. The government site [US-CERT](https://us-cert.cisa.gov/) (United States Computer Emergency Readiness Team) provides technical security alerts and tips.\n\n\nIf you're a Search Console user and are having trouble with persistent or unfixable security issues on your site, you can let us know.\n\n[Report a security issue](https://support.google.com/webmasters/contact/report_security_issues)"]]