It has been slightly more than a year that SOC Prime has been set on its current mission – to bring efficiency into most sophisticated Cyber Security technologies through automation, knowledge consolidation and fusion existing of market-leading technologies. Using the trendy phrases, we claimed that we would make “Cyber Security actionable” through automation of detection of known threats and by providing tools and freeing FTE to the combat the unknown ones. And while many companies out there strive for same purpose, we believe that no single solution or organization can battle the adversaries alone and there is clearly a need for collective defense system. Well, I am proud to announce that today we finished our first steps to make this goal come true. It is today that SOC Prime announces unification of our two core products, Predictive Maintenance for SIEM and Integration Framework, under a single platform for Security and Intelligence Management.
These days we can firmly state that current speed of security breach detection can be improved and it can be drastically lower than the infamous 200 days. And one of the first answers lies in automating many routine operations of a modern SOC and fusing together the technologies that have long been established in the industry. As many of you, our team has spent years in first-line operations of SIEM deployments and as many of you, we have gone through all the fun and challenging stuff of parser-writing, Use Case development, sizing, scoping, finding workarounds and making all these complex systems do what they are meant to – detect security incidents! Now if we think about this for a moment, an accurate detection depends on multiple factors including: availability of Log Data and external feeds, quality of the data consumed by SIEM that starts with correct parsing from the moment it is extracted from the log source and ends with categorization & enrichment, performance of the platform itself that needs a constant attention of its administrator, accuracy of asset and network information and last, but not least – security of the SIEM system itself.
All of this has been a thorough manual job for over a decade, and all of this is now changing as we apply more advanced toolsets to make our daily jobs easier and use our resources more efficient. This is what our Predictive Maintenance module is built for – improving the visibility into the heart of your SOC and giving you full insight and answers at an instant, right when you need them. There will be no more doubts or room for taking a wild guess on whether a SIEM has captured data you need and can provide it when it is needed, now you can rely on the facts and see a full picture at any point of time.
Yet, SIEM itself is but a piece of a solid security infrastructure and it needs to interconnect with a plethora of devices and security technologies. As noted by SANS in the beginning of 2015 more than 52% of companies responded to the SOC survey that they have little visibility into configurations and vulnerabilities of their assets that in turn reduces incident response efficiency. While vulnerability management and compliance assessment systems have been around since 1999 and have achieved a great success in both accuracy and speed of performing their jobs there is still a gap between operationalizing them when it comes to SOC. And this gap is closed through full integration of Vulnerability Management technologies with SIEM, and thus is one of first things we took care of via our Integration Framework.
Together with our first customers and partners we now prove in practice that framework is the basis for Continuous Vulnerability and Asset Monitoring. Now any company in the world can automate Vulnerability Management, Compliance & Configuration assessment platform operations in its SOC. Since not every company is the same when it comes to size, infrastructure, industry specifics and regulations, we have developed our platform to be available to all through pure SaaS and on-premise editions, deployable on VMware ESXi, Microsoft HyperV, Amazon AWS, KVM & Proxmox virtualization platforms. However, are the integration and automation going to take security as a whole to the next level of evolution? Not yet, and we have much more coming up in next few months. Stay tuned for updates!
Name | Descripiton |
---|---|
PHPSESSID | Preserves user session state across page requests. Cookie generated by applications based on the PHP language. This is a general purpose identifier used to maintain user session variables. It is normally a random generated number, how it is used can be specific to the site, but a good example is maintaining a logged-in status for a user between pages. |
sp_i | Used to store information about authenticated User. |
sp_r | Used to store information about authenticated User. |
sp_a | Used to store information about authenticated User. |
Name | Descripiton |
---|---|
tuuid | Collects anonymous data related to the user's visits to the website, such as the number of visits, average time spent on the website and what pages have been loaded. |
tuuid_last_update | Collects anonymous data related to the user's visits to the website, such as the number of visits, average time spent on the website and what pages have been loaded. |
um | Collects anonymous data related to the user's visits to the website, such as the number of visits, average time spent on the website and what pages have been loaded. |
umeh | Collects anonymous data related to the user's visits to the website, such as the number of visits, average time spent on the website and what pages have been loaded. |
na_sc_x | Used by the social sharing platform AddThis to keep a record of parts of the site that has been visited in order to recommend other parts of the site. |
APID | Collects anonymous data related to the user's visits to the website. |
IDSYNC | Collects anonymous data related to the user's visits to the website. |
_cc_aud | Collects anonymous statistical data related to the user's website visits, such as the number of visits, average time spent on the website and what pages have been loaded. The purpose is to segment the website's users according to factors such as demographics and geographical location, in order to enable media and marketing agencies to structure and understand their target groups to enable customised online advertising. |
_cc_cc | Collects anonymous statistical data related to the user's website visits, such as the number of visits, average time spent on the website and what pages have been loaded. The purpose is to segment the website's users according to factors such as demographics and geographical location, in order to enable media and marketing agencies to structure and understand their target groups to enable customised online advertising. |
_cc_dc | Collects anonymous statistical data related to the user's website visits, such as the number of visits, average time spent on the website and what pages have been loaded. The purpose is to segment the website's users according to factors such as demographics and geographical location, in order to enable media and marketing agencies to structure and understand their target groups to enable customised online advertising. |
_cc_id | Collects anonymous statistical data related to the user's website visits, such as the number of visits, average time spent on the website and what pages have been loaded. The purpose is to segment the website's users according to factors such as demographics and geographical location, in order to enable media and marketing agencies to structure and understand their target groups to enable customised online advertising. |
dpm | Via a unique ID that is used for semantic content analysis, the user's navigation on the website is registered and linked to offline data from surveys and similar registrations to display targeted ads. |
acs | Collects anonymous data related to the user's visits to the website, such as the number of visits, average time spent on the website and what pages have been loaded, with the purpose of displaying targeted ads. |
clid | Collects anonymous data related to the user's visits to the website, such as the number of visits, average time spent on the website and what pages have been loaded, with the purpose of displaying targeted ads. |
KRTBCOOKIE_# | Registers a unique ID that identifies the user's device during return visits across websites that use the same ad network. The ID is used to allow targeted ads. |
PUBMDCID | Registers a unique ID that identifies the user's device during return visits across websites that use the same ad network. The ID is used to allow targeted ads. |
PugT | Registers a unique ID that identifies the user's device during return visits across websites that use the same ad network. The ID is used to allow targeted ads. |
ssi | Registers a unique ID that identifies a returning user's device. The ID is used for targeted ads. |
_tmid | Registers a unique ID that identifies the user's device upon return visits. The ID is used to target ads in video clips. |
wam-sync | Used by the advertising platform Weborama to determine the visitor's interests based on pages visits, content clicked and other actions on the website. |
wui | Used by the advertising platform Weborama to determine the visitor's interests based on pages visits, content clicked and other actions on the website. |
AFFICHE_W | Used by the advertising platform Weborama to determine the visitor's interests based on pages visits, content clicked and other actions on the website. |
B | Collects anonymous data related to the user's website visits, such as the number of visits, average time spent on the website and what pages have been loaded. The registered data is used to categorise the users' interest and demographical profiles with the purpose of customising the website content depending on the visitor. |
1P_JAR | These cookies are used to gather website statistics, and track conversion rates. |
APISID | Google set a number of cookies on any page that includes a Google reCAPTCHA. While we have no control over the cookies set by Google, they appear to include a mixture of pieces of information to measure the number and behaviour of Google reCAPTCHA users. |
HSID | Google set a number of cookies on any page that includes a Google reCAPTCHA. While we have no control over the cookies set by Google, they appear to include a mixture of pieces of information to measure the number and behaviour of Google reCAPTCHA users. |
NID | Google set a number of cookies on any page that includes a Google reCAPTCHA. While we have no control over the cookies set by Google, they appear to include a mixture of pieces of information to measure the number and behaviour of Google reCAPTCHA users. |
SAPISID | Google set a number of cookies on any page that includes a Google reCAPTCHA. While we have no control over the cookies set by Google, they appear to include a mixture of pieces of information to measure the number and behaviour of Google reCAPTCHA users. |
SID | Google set a number of cookies on any page that includes a Google reCAPTCHA. While we have no control over the cookies set by Google, they appear to include a mixture of pieces of information to measure the number and behaviour of Google reCAPTCHA users. |
SIDCC | Security cookie to protect users data from unauthorised access. |
SSID | Google set a number of cookies on any page that includes a Google reCAPTCHA. While we have no control over the cookies set by Google, they appear to include a mixture of pieces of information to measure the number and behaviour of Google reCAPTCHA users. |
__utmx | This cookie is associated with Google Website Optimizer, a tool designed to help site owners improve their wbesites. It is used to distinguish between two varaitions a webpage that might be shown to a visitor as part of an A/B split test. This helps site owners to detemine which version of a page performs better, and therefore helps to improve the website. |
__utmxx | This cookie is associated with Google Website Optimizer, a tool designed to help site owners improve their wbesites. It is used to distinguish between two varaitions a webpage that might be shown to a visitor as part of an A/B split test. This helps site owners to detemine which version of a page performs better, and therefore helps to improve the website. |
Name | Descripiton |
---|---|
_hjid | Hotjar cookie. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_hjIncludedInSample | This cookie is associated with web analytics functionality and services from Hot Jar, a Malta based company. It uniquely identifies a visitor during a single browser session and indicates they are included in an audience sample. |
intercom-id-[xxx] | This cookie is used by Intercom as a session so that users can continue a chat as they move through the site. |
intercom-session-[xxx] | Used to keeping track of sessions and remember logins and conversations. |
demdex | Via a unique ID that is used for semantic content analysis, the user's navigation on the website is registered and linked to offline data from surveys and similar registrations to display targeted ads. |
CookieConsent | Stores the user's cookie consent state for the current domain. |
__cfduid | Used by the content network, Cloudflare, to identify trusted web traffic. |
ss | These cookies enable the website to provide enhanced functionality and
personalisation . They may be set by us or by third party providers whose
services we have added to our pages. These services may include the Live Chat facility, Contact Us form(s), the Product Quotation forms and submission process, and the Email Newsletter sign up functionality . |
Name | Descripiton |
---|---|
_ga | This cookie name is asssociated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page. Registers a unique ID that is used to generate statistical data on how the visitor uses the website. request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners. |
_gat | Used by Google Analytics to throttle request rate. This cookie name is associated with Google Universal Analytics, according to documentation it is used to throttle the request rate - limiting the collection of data on high traffic sites. It expires after 10 minutes. |
_gid | This cookie name is asssociated with Google Universal Analytics. This appears to be a new cookie and as of Spring 2017 no information is available from Google. It appears to store and update a unique value for each page visited. Registers a unique ID that is used to generate statistical data on how the visitor uses the website. |
IDE | Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user. |
r/collect | Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user. |
test_cookie | Used to check if the user's browser supports cookies. |
collect | Used to send data to Google Analytics about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. |
ads/user-lists/# | These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. |
c | Registers anonymised user data, such as IP address, geographical location, visited websites, and what ads the user has clicked, with the purpose of optimising ad display based on the user's movement on websites that use the same ad network. |
khaos | Registers anonymised user data, such as IP address, geographical location, visited websites, and what ads the user has clicked, with the purpose of optimising ad display based on the user's movement on websites that use the same ad network. |
put_# | Registers anonymised user data, such as IP address, geographical location, visited websites, and what ads the user has clicked, with the purpose of optimising ad display based on the user's movement on websites that use the same ad network. |
rpb | Registers anonymised user data, such as IP address, geographical location, visited websites, and what ads the user has clicked, with the purpose of optimising ad display based on the user's movement on websites that use the same ad network. |
rpx | Registers anonymised user data, such as IP address, geographical location, visited websites, and what ads the user has clicked, with the purpose of optimising ad display based on the user's movement on websites that use the same ad network. |
tap.php | Registers anonymised user data, such as IP address, geographical location, visited websites, and what ads the user has clicked, with the purpose of optimising ad display based on the user's movement on websites that use the same ad network. |