Anti-Spyware Coalition

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Anti-Spyware Coalition" – news · newspapers · books · scholar · JSTOR (October 2014) (Learn how and when to remove this template message)

It is proposed that this article be deleted because of the following concern:

No evidence of notability (proposed by Pppery)

If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it.

The article may be deleted if this message remains in place for seven days, i.e., after 16:44, 4 May 2024 (UTC).

If you created the article, please don't be offended. Instead, consider improving the article so that it is acceptable according to the deletion policy.
Find sources: "Anti-Spyware Coalition" – news · newspapers · books · scholar · JSTOR

Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Anti-Spyware Coalition|concern=No evidence of notability}} ~~~~

The Anti-Spyware Coalition (ASC) was a group formed in 2005 with the goal to build a consensus about definitions and best practices in the debate surrounding spyware.

Composed of anti-spyware software companies, academics, and consumer groups, the ASC seeks to bring together a diverse array of perspective on the problem of controlling spyware and other potentially unwanted technologies.

History[edit]

Formed in 2005 after the dissolution of the Consortium of Anti-Spyware Technology Vendors (COAST) which broke up over internal dissent.^[1] In April 2005 Ari Schwartz called together the initial group of Anti-Spyware companies; others later joined. A series of documents was published, and feedback solicited. The first set of documents consisted of a definition of spyware and potentially unwanted technologies, and a vendor dispute resolution process. This was followed by a "Risk Model" providing Anti-Spyware vendors with a framework for classifying software. In March 2007 the ASC published the public final draft of their Best Practices document.^{[citation needed]}

References[edit]

^ Cowley, Stacy, "Coast antispyware consortium falls apart", IDG News Service, http://www.infoworld.com/article/05/02/08/HNcoastfallsapart_1.html February 8, 2005 Archived February 28, 2007, at the Wayback Machine

External links[edit]

Anti-spyware guidelines get final version

v t e Malware topics
Infectious malware	Comparison of computer viruses Computer virus Computer worm List of computer worms Timeline of computer viruses and worms
Concealment	Backdoor Clickjacking Man-in-the-browser Man-in-the-middle Rootkit Trojan horse Zombie computer
Malware for profit	Adware Botnet Crimeware Fleeceware Form grabbing Fraudulent dialer Malbot Keystroke logging Privacy-invasive software Ransomware Rogue security software Scareware Spyware Web threats
By operating system	Android malware Classic Mac OS viruses iOS malware Linux malware MacOS malware Macro virus Mobile malware Palm OS viruses HyperCard viruses
Protection	Anti-keylogger Antivirus software Browser security Data loss prevention software Defensive computing Firewall Internet security Intrusion detection system Mobile security Network security
Countermeasures	Computer and network surveillance Honeypot Operation: Bot Roast

This article about a business, industry, or trade-related organization is a stub. You can help Wikipedia by expanding it.