130 likes | 145 Views
A proposal for establishing a national anti-spam infrastructure in Malaysia, focusing on collaboration among internet service providers for effective spam resolution. The model includes blacklist and whitelist systems, information sharing, and a moderated platform for resolving spam complaints. Long-term objectives include close cooperation among service providers and national-level representation for abuse issues.
E N D
Anti-Spam Management for Service Provider in Malaysia Alan Lee NTT MSC
Background • Working group of the ISF • TIME, Maxis, Jaring, NTT MSC • Need for collaboration among the IASP at National level • To Combat Spam
Objectives • To establish a national anti-spam efforts • Inter IASP Cooperation • Resolutions of Spam • To define common processes • To present a serious effort and penalties for spamming • Best current practices • Technical framework for action • Implement a national anti-spam infrastructure • Education
Spam Spam Spam Global Internet Service Provider Service Provider Service Provider Current Model • Different policies • Inconsistent results • No cooperation • No representation • Spammers playground • No control to register spam source or de-list
Spam Spam Spam Global Internet Local RBL Service Portal Reports Local Anti-spam Platform Service Provider Service Provider Service Provider Proposed Model • Local Database • Use of Whitelist and Backlist • Information Sharing • Collaboration • Useful reports • Moderated • National level representation
Y N Whitelisted? Blacklisted Global RBL N N Y Y Whitelist lookup to allow mails within main mail servers Blacklist lookup Based on recommended RBL Mail allowed through of dropped Mail Filtering Algorithm Accept mail Y Incoming mail Override? N Deny mail Local RBL Special allow/deny list. Eg. Internal mail servers
Request for Assistance on LAP N Issue warning Request to be Blacklist Internal customer? Solved? Y N Y Share solution on portal if necessary Identify if source is a customer Issue warning to customer to rectify issue Most issue would have been solved at this stage Request to be blacklisted is always worst case scenario Service Provider Process Spam Complaint Source from either e-mail, newsgroup, portal
Request for de-listing Request posted for approval Blacklisted De-listed Approved? Resolved? Y Y N N Posting on the portal or newsgroup 2/3 of members vouch the claim or no objections from others Blacklisted for 2 weeks before review again If not resolved, permanent blacklisting is proposed IP Address removed from Blacklist Listing and De-listing Process Request for listing By a ISAP member
Effects of Blacklisting • Mails will be denied delivery by local service providers • Deny spammers from moving to other service providers • Suspension of services • Trial under Section 233, network abuse
Requirements • Technical • Web front for posting • DNS Server for blacklisting propagation • Whois server for maintaining local contact • Reporting server • Processes • Secure information sharing between ISF members • Active participation from individual abuse teams • Moderated by MCMC
Concerns • Online marketing companies might be affected • Suspending user accounts might not be the best interest of the company • Difficult to track spammer who uses public hotspots and cybercafe • Not all ISF members will agree on policies introduced
Long Term Objectives • Close cooperation between ISAP for effective resolution to abuse issues • Provide national level representation in terms of contact point for abuse issues • Law against spam