Bloggers Paradise

Cannot impersonate user for data source ‘CDRDB’. (rsErrorImpersonatingUser) error

rsErrorImpersonatingUser

While Configuring Lync Server: You get the above error when you click on reports or configure reports.

So what do you do ?

Solution:

Start by checking the following items:

SQL permissions for the user being used for reporting purpose.
AD Groups membership of the User
Permission on SSRS for the User
Permission on LYNC reports
Check Web applications on IIS (if windows auth is enabled)

Finally check if the account had a valid connection from SSRS to DB.

Perform the below steps:

Open Reporting Services Configuration Manager
Click on Report Manager URL
Click Report URL (This will launch IE which I hope if your default browser)
Drill into
LyncServerReports
Reports_Content

Update the username and password: for the Lync report database.(do the same for both the database) as shown below:

Hacking rose by 92% this year

With hacking on the rise by 92% this year, it's time to ditch the old approach to stopping cyber attacks and get protected.

Hacking rose by 92% this year
Malware attacks were up by 57%
Antivirus stops only 1 of 4 targeted attacks
94% of advanced threats target the data on enterprise servers
In a recent survey, 60% of organizations were unaware they had even been hacked
In the same study, nearly 50 % of breaches targeted desktops, laptops, and POS terminals
Signature updates can cripple your systems
Customers would be trusting Companies with their personal data.

Its time to change !!!!

Simple go for a organization anti-virus or an enterprise anti-virus program that can help you achieve Momentum and results in short time.

Reduce costs, risks, and maintain compliance for a 'Get better protection tomorrow'.

Domain Name System Security Extensions (DNSSEC)

DNSSEC what it really means and how is it related to us......

DNSSEC (short for DNS Security Extensions) adds security to the Domain Name System

DNSSEC

Domain Name System Security Extension (DNSSEC) will help strengthen trust in the Internet by helping to protect users from redirection to fraudulent web sites and unintended addresses.

DNSSEC was designed to protect the Internet from certain attacks, such as DNS cache poisoning [0]. It is a set of extensions to DNS, which provide: a) origin authentication of DNS data, b) data integrity, and c) authenticated denial of existence.

These mechanisms require changes to the DNS protocol. DNSSEC adds four new resource record types: Resource Record Signature (RRSIG), DNS Public Key (DNSKEY), Delegation Signer (DS), and Next Secure (NSEC). These new RRs are described in detail in RFC 4034.

DNSSEC is the only solution that solves the DNS cache poisoning security hole, conclusively. Many top-level zones, including .ARPA, .GOV and .ORG, as well as the root zone, have already been signed using DNSSEC. This new technological strategy allows appropriately configured name servers to validate answers cryptographically from these zones—effectively eliminating the possibility of cache poisoning. In the coming months, many additional zones will be signed, including .NET and .COM. Now, every organization needs to assess its DNSSEC implementation drivers and readiness, and develop a DNSSEC policy and implementation plan. Infoblox can help your organization develop its DNSSEC policy and implementation plan today. However DNSSEC does not provide confidentiality of data at any time and does not protect against DDoS Attacks.There are a lot of tools available in the market that support DNSSEC you can just try goggling it out.

To make deployment of DNSSEC easier, one can also buy a dedicated "DNSSEC Appliance", which acts as an automated DNS signer for DNS zones. Several vendors are already offering commercial and non-commercial solutions for signing DNS in real time, some of them using external cryptographic hardware such as HSM (Hardware Security Modules), including USB tokens and smart cards.

Several ISPs have started to deploy DNSSEC-validating DNS recursive resolvers. Comcast became the first major ISP to do so in the United States, announcing their intentions on October 18, 2010 and completing deployment on January 11, 2012.

Key Benefits after implementing DNSSEC:-

Accelerated path to security and compliance
Lower operational costs and expertise risks
Reduced configuration errors to ensure service availability

There's a mobile app for the DNSSEC Analyzer:-

There a lot that I can talk on DNSSEC, more information can be found here

More information about DNS Weaknesses can be found in the DNS Threats section.