<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>security &#8211; it.megocollector.com</title>
	<atom:link href="https://it.megocollector.com/tag/security/feed/" rel="self" type="application/rss+xml" />
	<link>https://it.megocollector.com</link>
	<description>The information technology compendium</description>
	<lastBuildDate>Thu, 07 May 2026 21:00:22 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>How to adapt the scap-security-guide for DISA CIS for CentOS8 Linux</title>
		<link>https://it.megocollector.com/linux/how-to-adapt-the-scap-security-guide-for-disa-cis-for-centos8-linux/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Fri, 18 Dec 2020 12:49:40 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[CentOS]]></category>
		<category><![CDATA[cui]]></category>
		<category><![CDATA[rhel]]></category>
		<category><![CDATA[scap]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[stig]]></category>
		<guid isPermaLink="false">https://it.megocollector.com/?p=4538</guid>

					<description><![CDATA[The scap-security-guide changes in format with each new guide.&#160; CentOS 8 is not fully represented within the guide.&#160; The XMLs provided differ in context, so the RHEL XML must be used to generate the report but requires a small patch to do so. The CUI Profile The ssg-rhel8-ds-1.2.xml contains the profile cui, while the one for ssg-centos8-ds-1.2.xml does not. [root@admin...]]></description>
		
		
		
			</item>
		<item>
		<title>Install duo client on CentOS</title>
		<link>https://it.megocollector.com/linux/install-duo-client-on-centos/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Thu, 21 Nov 2019 18:54:28 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[dual-factor-authentication]]></category>
		<category><![CDATA[duo]]></category>
		<category><![CDATA[security]]></category>
		<guid isPermaLink="false">https://it.megocollector.com/?p=4292</guid>

					<description><![CDATA[DUO is a self-described &#8220;easy-to-use&#8221; two-factor authentication method that protects access to federated cloud and on-premises applications and servers.&#160; DUO offers several pricing plans and a free tier.&#160; The free tier is quite generous providing dual factor authentication to up to 10 users.&#160;&#160; This article assumes that you have created a DUO account, logged into the admin dashboard and ready...]]></description>
		
		
		
			</item>
		<item>
		<title>Create an Ansible script for DISA STIG and execute it in CentOS 7</title>
		<link>https://it.megocollector.com/scripts/create-an-ansible-script-for-disa-stig-and-execute-it-in-centos-7/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sun, 29 Sep 2019 23:02:05 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Scripts]]></category>
		<category><![CDATA[ansible]]></category>
		<category><![CDATA[disa]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[stig]]></category>
		<guid isPermaLink="false">https://it.megocollector.com/?p=4198</guid>

					<description><![CDATA[Securing a CentOS 7 install doesn&#8217;t have to be tough.  Code already exists, we just have to find it and execute it. Prerequisites yum install openscap scap-security-guide -y Verification The version of the scap-security-guide that was tested is 0.1.40. Version 0.1.43 has removed the DISA STIG from the CentOS guide ssg-centos7-ds.xml; however, there is a work-a-round. Article coming soon. scap-security-guide.noarch...]]></description>
		
		
		
			</item>
		<item>
		<title>Microsoft Windows XP cannot access Vista share</title>
		<link>https://it.megocollector.com/tips-and-tricks/microsoft-windows-xp-cannot-access-vista-share/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Wed, 02 Sep 2009 13:13:21 +0000</pubDate>
				<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[share]]></category>
		<category><![CDATA[vista]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[xp]]></category>
		<guid isPermaLink="false">https://it.megocollector.com/?p=1216</guid>

					<description><![CDATA[The situation is common. In the past, shared access between computers rather they be Linux, Windows 98, Windows Me, Windows 2000, Windows NT, or Windows XP is a relatively painless and simple process. However, recently, I have encountered increadible difficulty accessing a share from a Windows XP Professional to a Windows Vista share. At first, I thought it to because...]]></description>
		
		
		
			</item>
		<item>
		<title>Microsoft Word Accept and Reject Change Options Greyed Out</title>
		<link>https://it.megocollector.com/tips-and-tricks/microsoft-word-accept-and-reject-change-options-greyed-out/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 10 Mar 2009 15:59:11 +0000</pubDate>
				<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[file sharing options]]></category>
		<category><![CDATA[microsoft word]]></category>
		<category><![CDATA[protect document]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[track changes]]></category>
		<guid isPermaLink="false">https://it.megocollector.com/?p=1108</guid>

					<description><![CDATA[There is a feature in Microsoft Word that allows one to &#8220;track changes&#8221;. Using the Track Changes and Comments features in Microsoft Word, one can enable others to edit or add comments to the document without the original text being changed and, when the document is returned, any editing changes that have been made may be accepted or rejected. Recently,...]]></description>
		
		
		
			</item>
		<item>
		<title>Symantec Client Security 2.0 silent install script</title>
		<link>https://it.megocollector.com/software-packaging/symantec-client-security-20-silent-install-script/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Thu, 11 May 2006 23:48:00 +0000</pubDate>
				<category><![CDATA[Scripts]]></category>
		<category><![CDATA[Software Packaging]]></category>
		<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[2.0]]></category>
		<category><![CDATA[client]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[silent install]]></category>
		<category><![CDATA[Symantec]]></category>
		<guid isPermaLink="false">https://it.megocollector.com/?p=15</guid>

					<description><![CDATA[The original script to install Symantec Client Security 2.0 will not execute in a silent installation. Original script msiexec /i "Symantec Client Security.msi" WSCAVALERT=0 WSCFWALERT=0 setup.exe /s /v" /qn INSTALLSERVER=0 MIGRATESETTINGS=0 REBOOT=ReallySuppress" Modified script cmd /c SCS.msi /qn LIVEUPDATE=0 MIGRATESETTINGS=0 REBOOT=REALLYSUPPRESS]]></description>
		
		
		
			</item>
	</channel>
</rss>
