Re: Default Hidden login/password?

From: John (jonashbaugh@hotmail.com)
Date: 12/20/02 

From: "John" <jonashbaugh@hotmail.com>
Date: Fri, 20 Dec 2002 12:52:25 -0800

Jasper,

        We currently have a beta tester that is using our application / sql
server solution. I was using the sa login to login to the server from our
office. Since you're saying that this is bad...any other solutions to my
dilemma? I have the ability to pcanywhere into the server as well. We are
also setting up replication between the server here and at the clients. What
other security issues should I be aware of? Should I deny access to sa? Any
additional input would be most appreciated.

John

"Jasper Smith" <jasper_smith9@hotmail.com> wrote in message
news:#f8AafFqCHA.2796@TK2MSFTNGP10...
> If you are not using IPSEC or SSL anyone with the
> ability to search google can easily find out how to grab
> the password off the wire. The "encryption" for SQL
> passwords during a connect is tantamount to plain text,
> it's that easy to decipher. The benefit of using NT logins
> is that no password is transmitted to the server. It also
> allows better auditing of changes to the server if you have
> multiple administrators. It's easy enough to set up a local
> group on the server (e.g. SERVER\SQLDBA) and add
> your admins to that NT group and then grant access to
> SQL for that group and add it to the sysadmin role. If it's
> just you then just add a login for your NT account.
> Whilst you may well have firewalls in place, internal hacking
> is a growing threat and since it is so straightforward to hack
> SQL login passwords, it makes sense not to use them,
> especially for high risk accounts like sa.
>
> --
> HTH
>
> Jasper Smith (SQL Server MVP)
>
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> "John" <jonashbaugh@hotmail.com> wrote in message
> news:#R0IFIFqCHA.2252@TK2MSFTNGP12...
> > I have set up deny for BUILTIN\Administrators. I login using the sa
> account.
> > Bad idea? Why? Thanks in advance. Our sa password is over 12 characters
> > long.
> >
> > "Jasper Smith" <jasper_smith9@hotmail.com> wrote in message
> > news:OTlgDkEqCHA.2764@TK2MSFTNGP09...
> > > No, not hidden but there are 2 default logins
> > >
> > > 1) sa - built in sysadmin SQL login - make sure it has
> > > a very strong password and don't use it ever.
> > > 2) BUILTIN\Administrators - NT group that maps to
> > > the local administrators group on the server. Sysadmin
> > > rights by default.
> > >
> > > --
> > > HTH
> > >
> > > Jasper Smith (SQL Server MVP)
> > >
> > > I support PASS - the definitive, global
> > > community for SQL Server professionals -
> > > http://www.sqlpass.org
> > >
> > > "John" <jonashbaugh@hotmail.com> wrote in message
> > > news:OSCIqFEqCHA.1776@TK2MSFTNGP09...
> > > > Is there a default hidden login and password like there is in
Oracle?
> I
> > > want
> > > > to make sure that the server is secure. Thanks.
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: SQL User SID format?
    ... When you move databases to another server, you can remap users to logins ... capability to remap a user to a login with new ALTER USER syntax - I ... The new ALTER USER syntax works for remapping both SQL and Windows ... this means you already have access to a SID from the syslogins catalog; ...
    (microsoft.public.sqlserver.security)
  • Re: SQL Server on XP Home Network
    ... The sa account is the system administrator "God" account witihin SQL ... This account is a SQL-Server login. ... You might be able to use Enterprise Manager to go in and create a new SQL ... Select the "SQL Server Authentication" ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL Server 2000 Replication Agents Credentials
    ... the snapshot agent IS using sql login to connect to the ... The pull distribution agent IS using sql ... Do you know where SQL Server 2000 saves the sql ...
    (microsoft.public.sqlserver.replication)
  • Re: Can you update/process AS2005 cube with AMO and SQL authentica
    ... We have cases where the AS server and the Data Source server reside on 2 ... The data source is properly secured using SQL Server ... login and no serious client will accept the login with no password. ...
    (microsoft.public.sqlserver.olap)
  • Login failed for user (null). Reason: Not associated with a trus
    ... I'm running SQL 2000 on two machines, one developer edition, one standard. ... server, running windows 2000 server. ... Basicly for troubleshooting, I also have tried using the sa Login, ...
    (microsoft.public.dotnet.framework.aspnet.security)
Quantcast